Closed Bug 1464538 Opened 7 years ago Closed 6 years ago

[wpt-sync] Sync PR 11173 - [testdriver] Enable manual interaction

Categories

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

Product:
Testing
Component:
web-platform-tests
Type:
enhancement

Tracking

(firefox67 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla67
Tracking Flags:
Tracking Status
firefox67 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 11173 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/w3c/web-platform-tests/pull/11173 Details from upstream follow. Mike Pennisi <mike@mikepennisi.com> wrote: > [testdriver] Enable manual interaction > > The testdriver.js utility allows tests which require user input to be > fully automated. It requires that the browser be under the control of a > WebDriver server in order to do this. > > In test maintenance contexts, this requirement can slow development > because a new browsing session must be created for each trial, and > debugging tools such as the developer's console cannot be used. > > This requirement also limits the tests' value to a larger audience when > published online. Visitors to sites like w3c-test.org are interested in > observing test results experimentally, but although they may be capable > of providing the expected input, the hard requirement on WebDriver will > cause tests to fail unconditionally. > > Extend the framework to accept traditional human input if the test is > being run without the WebDriver technology. This allows test authors to > debug tests and other interested parties to verify results in browsers > of their choosing. It does not interfere with fully-automated test > execution. > > --- > > @gsnedders @kereliuk I'm interested in going even further with this. We could make testdriver.js-powered tests look a lot like today's manual tests by dynamically inserting instructions for human operators. That's less compelling for test authors (since they presumably know exactly what inputs are needed by their own tests), but it could make a big difference for visitors to http://w3c-test.org. > > Of course, any change to the document has the potential to invalidate the test, so it would need to be configurable. > > For now, I figured this would be a simple and safe way to make test author's lives a little easier. > > I'm excited to start extending tests with testdriver.js. Thanks for making it possible!
Whiteboard: [wptsync downstream] → [wptsync downstream error]
PR 11173 applied with additional changes from upstream: 8908785565303fd7ab90afb30dda868239401895
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/2e1f864ca504 [wpt PR 11173] - [testdriver] Enable manual interaction, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/66fb4cc72692 [wpt PR 11173] - Update wpt metadata, a=testonly
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/8dab7dd839f4 [wpt PR 11173] - [testdriver] Enable manual interaction, a=testonly https://hg.mozilla.org/integration/mozilla-inbound/rev/750c255d2aab [wpt PR 11173] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/8dab7dd839f4
https://hg.mozilla.org/mozilla-central/rev/750c255d2aab

Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox67: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.