Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[wptrunner] Plumb expectations wpttest.{Test -> (Subtest)Result} #44424

Merged

Conversation

jonathan-j-lee
Copy link
Contributor

@jonathan-j-lee jonathan-j-lee commented Feb 6, 2024

This allows vendors to override expectations at runtime via
browser-specific result converters. Instead of constructing
(Subtest)Results directly, executors should use the newly introduced
Test.make_{subtest_,}result(), which have the same signatures but
default to passing through the testloader-read expectations.

This is a pure refactor; no functional changes intended.

Successor to: #44134 (comment)

This allows vendors to override expectations at runtime via
browser-specific result converters. Instead of constructing
`(Subtest)Result`s directly, executors should use the newly introduced
`Test.make_{subtest_,}result()`, which have the same signatures but
default to passing through the testloader-read expectations.

This is a pure refactor; no functional changes intended.

Successor to: web-platform-tests#44134 (comment)
@jonathan-j-lee jonathan-j-lee marked this pull request as ready for review February 6, 2024 20:49
@wpt-pr-bot wpt-pr-bot added infra wptrunner The automated test runner, commonly called through ./wpt run labels Feb 6, 2024
@jonathan-j-lee jonathan-j-lee merged commit a68f313 into web-platform-tests:master Feb 6, 2024
33 checks passed
@jonathan-j-lee jonathan-j-lee deleted the wptrunner/plumb-exp branch February 6, 2024 23:15
mbrodesser-Igalia pushed a commit to mbrodesser-Igalia/wpt that referenced this pull request Feb 19, 2024
…eb-platform-tests#44424)

This allows vendors to override expectations at runtime via
browser-specific result converters. Instead of constructing
`(Subtest)Result`s directly, executors should use the newly introduced
`Test.make_{subtest_,}result()`, which have the same signatures but
default to passing through the testloader-read expectations.

This is a pure refactor; no functional changes intended.

Successor to: web-platform-tests#44134 (comment)
marcoscaceres pushed a commit that referenced this pull request Feb 23, 2024
…44424)

This allows vendors to override expectations at runtime via
browser-specific result converters. Instead of constructing
`(Subtest)Result`s directly, executors should use the newly introduced
`Test.make_{subtest_,}result()`, which have the same signatures but
default to passing through the testloader-read expectations.

This is a pure refactor; no functional changes intended.

Successor to: #44134 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infra wptrunner The automated test runner, commonly called through ./wpt run
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants