New issue
Advanced search Search tips

Issue 898051 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Document instructions for debugging content_shell locally with wpt

Project Member Reported by dcheng@chromium.org, Oct 23

Issue description

I periodically need to debug wpt and I generally end up having to reverse engineer the debugging process each time.

Ideally, the README.md in external/wpt would also document these steps. Useful things would be:
- how to run wpt locally (using run_blink_wptserve.py)
- how to set up hosts (without checking out upstream wpt)
- the command-line invocation for running an actual test
 
Status: Available (was: Untriaged)
I suspect this is documented in WPT proper. Maybe stable subsection labels would allow us to link to appropriate instructions. Would that be sufficient?
I don't think WPT's documentation covers this, as WPT essentially assumes we're going to launch Chrome, not content_shell. It'd be good to have those instructions in e.g. //docs/testing/web_platform_tests.md (for instance, trying to invoke content_shell directly and run an HTTPS test is always a PITA).

Sign in to add a comment