openstf/stf

Add Chrome direct debug support (without requiring to install ADB)

Open

#10 opened on Jul 13, 2015

View on GitHub
 (4 comments) (0 reactions) (0 assignees)JavaScript (13,038 stars) (2,705 forks)batch import
enhancementhelp wanted

Description

I submitted a ticket here 1 year ago, but current status is WontFix because "We are experimenting with alternative ways of implementing wireless debugging".

As long as there is any update on this, we need to update this ticket.

Contributor guide

Tech stack
javascriptnodejs
Domain
mobiletooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Chrome DevTools ProtocolAndroid debuggingNode.jsWebSocket
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
The Chromium issue (https://code.google.com/p/chromium/issues/detail?id=388206) notes that wireless debugging alternatives are being explored. Research the Chrome DevTools Protocol (CDP) to see if direct debugging without ADB is possible via WebSocket. Examine the STF codebase, particularly the device driver modules (e.g., lib/units/device/), to understand how ADB is currently used and how to integrate an alternative transport.