[testharness.js] Implement single_test option#19449
Merged
foolip merged 3 commits intoweb-platform-tests:masterfrom Oct 7, 2019
Merged
[testharness.js] Implement single_test option#19449foolip merged 3 commits intoweb-platform-tests:masterfrom
single_test option#19449foolip merged 3 commits intoweb-platform-tests:masterfrom
Conversation
The behavior and deployment schedule of this option was defined via the following web-platform-tests RFC: https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
Contributor
Author
|
The website cannot currently be re-generated due to an unrelated bug in the content of the documentation. gh-19403 fixes that, but the changes in this (or any other) pull request will not be deployed until that is merged. |
Member
|
See #19303 for another fix related to the broken docs. |
foolip
reviewed
Oct 1, 2019
foolip
approved these changes
Oct 7, 2019
| * function object, it will be | ||
| * serialized to a string using the | ||
| * built-in | ||
| * `Function.prototype.toString` prior |
Member
There was a problem hiding this comment.
The value is stringified like any other, which will probably involve Function.prototype.toString, but if toString is an own property on the function object directly, that will be used instead. This makes the documentation not strictly true, but I have to admit there's value in pointing out what the stringifier likely is.
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 26, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 26, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 26, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 26, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 26, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 26, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 26, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 26, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 26, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 26, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 27, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to instead declare a single subtest (so that it is no longer a single-page test). [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 27, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to instead declare a single subtest (so that it is no longer a single-page test). [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 27, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update some tests which previously opted in implicitly to use the new API. Update others to instead declare a single subtest (so that it is no longer a single-page test). [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 27, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update some tests which previously opted in implicitly to use the new API. Update others to instead declare a single subtest (so that they are no longer single-page tests). [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 27, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update some tests which previously opted in implicitly to use the new API. Update others to instead declare a single subtest (so that they are no longer single-page tests). [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
foolip
pushed a commit
that referenced
this pull request
Oct 27, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update some tests which previously opted in implicitly to use the new API. Update others to instead declare a single subtest (so that they are no longer single-page tests). [1] #19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
foolip
pushed a commit
that referenced
this pull request
Oct 27, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to instead declare a single subtest (so that it is no longer a single-page test). [1] #19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
foolip
pushed a commit
that referenced
this pull request
Oct 27, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to instead declare a single subtest (so that it is no longer a single-page test). [1] #19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
foolip
pushed a commit
that referenced
this pull request
Oct 28, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] #19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 29, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update some tests which previously opted in implicitly to use the new API. Update others to instead declare a single subtest (so that they are no longer single-page tests). [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
that referenced
this pull request
Oct 29, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update some tests which previously opted in implicitly to use the new API. Update others to instead declare a single subtest (so that they are no longer single-page tests). [1] #19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 30, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update some tests which previously opted in implicitly to use the new API. Update others to instead declare a single subtest (so that they are no longer single-page tests). [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
that referenced
this pull request
Oct 30, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update some tests which previously opted in implicitly to use the new API. Update others to instead declare a single subtest (so that they are no longer single-page tests). [1] #19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 30, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update some tests which previously opted in implicitly to use the new API. Update others to instead declare a single subtest (so that they are no longer single-page tests). Add new tests to fully cover the conditions under which an uncaught exception or unhandled rejection could occur. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
that referenced
this pull request
Oct 30, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update some tests which previously opted in implicitly to use the new API. Update others to instead declare a single subtest (so that they are no longer single-page tests). Add new tests to fully cover the conditions under which an uncaught exception or unhandled rejection could occur. [1] #19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Oct 31, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
foolip
pushed a commit
that referenced
this pull request
Oct 31, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] #19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
jugglinmike
added a commit
to bocoup/wpt
that referenced
this pull request
Nov 7, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update a test which previously opted in implicitly to use the new API. [1] web-platform-tests#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
foolip
pushed a commit
that referenced
this pull request
Nov 8, 2019
testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update a test which previously opted in implicitly to use the new API. [1] #19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md
bors-servo
pushed a commit
to servo/servo
that referenced
this pull request
Nov 15, 2019
Address upstream WPT test harness changes web-platform-tests/wpt#19449 and web-platform-tests/wpt#19993 caused some of our proprietary tests to silently start to fail. This addresses all of the breakage.
bors-servo
pushed a commit
to servo/servo
that referenced
this pull request
Nov 15, 2019
Address upstream WPT test harness changes web-platform-tests/wpt#19449 and web-platform-tests/wpt#19993 caused some of our proprietary tests to silently start to fail. This addresses all of the breakage.
bors-servo
pushed a commit
to servo/servo
that referenced
this pull request
Nov 15, 2019
Address upstream WPT test harness changes web-platform-tests/wpt#19449 and web-platform-tests/wpt#19993 caused some of our proprietary tests to silently start to fail. This addresses all of the breakage.
bors-servo
pushed a commit
to servo/servo
that referenced
this pull request
Nov 15, 2019
Address upstream WPT test harness changes web-platform-tests/wpt#19449 and web-platform-tests/wpt#19993 caused some of our proprietary tests to silently start to fail. This addresses all of the breakage.
bors-servo
pushed a commit
to servo/servo
that referenced
this pull request
Nov 16, 2019
Address upstream WPT test harness changes web-platform-tests/wpt#19449 and web-platform-tests/wpt#19993 caused some of our proprietary tests to silently start to fail. This addresses all of the breakage.
bors-servo
pushed a commit
to servo/servo
that referenced
this pull request
Nov 16, 2019
Address upstream WPT test harness changes web-platform-tests/wpt#19449 and web-platform-tests/wpt#19993 caused some of our proprietary tests to silently start to fail. This addresses all of the breakage.
bors-servo
pushed a commit
to servo/servo
that referenced
this pull request
Nov 16, 2019
Address upstream WPT test harness changes web-platform-tests/wpt#19449 and web-platform-tests/wpt#19993 caused some of our proprietary tests to silently start to fail. This addresses all of the breakage.
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this pull request
Nov 20, 2019
…ture, a=testonly Automatic update from web-platform-tests [FileAPI] Opt-in to single-page test feature (#19925) testharness.js was recently extended with an API to explicitly opt-in to the "single page test" feature [1]. As per WPT RFC 28 [2], tests which do not use this API and which do not declare any subtests will soon be reported as a harness error. Update the tests which previously opted in implicitly to use the new API. [1] web-platform-tests/wpt#19449 [2] https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md -- wpt-commits: 89ebe927c237ed05c732490ca7d82b7fc41f5908 wpt-pr: 19925 Differential Revision: https://phabricator.services.mozilla.com/D53490
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The behavior and deployment schedule of this option was defined via the
following web-platform-tests RFC:
https://github.com/web-platform-tests/rfcs/blob/master/rfcs/single_test.md