1692204 - Allow running chrome js after tests fails to dump internal state

Status: NEW

(Testing :: web-platform-tests, enhancement, P3)

Description

[James Graham [:jgraham]]

The idea is in systems with significant internal state it could be useful to dump that state when a test fails. This can generically be implemented by allowing running js in the parent process after the test fails.

For performance reasons we probably only want to do this for unexpected failures; if we're trying to debug something on try it's always possible to setup the failure to be unexpected.

Comment 1

[James Graham [:jgraham]]

Attachment: Bug 1692204 - Support running chrome js after unexpected wpt failures

The intent is that scripts can be provided that will dump internal
state after a test fails. The scripts are provided in the metadata
using a syntax like

debug-scripts: [script1.js, script2.js]

The script paths are resolved relative to the --debug-scripts-root
command line option, which is set to
$SRCDIR/testing.web-platform/scripts when running via mach.

The scripts may return a string result which will be logged from the
harness.

Comment 2

[James Graham [:jgraham]]

Attachment: Bug 1692204 - Example of using debug-scripts