-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Implement assert_implements and assert_implements_optional #22699
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
Conversation
See web-platform-tests/rfcs#48 and #21971. Note that this PR only implements the new methods; it does not port any tests to use it or remove `assert_precondition` - that will be done in follow-up PRs.
I couldn't figure out if there's a place for unittests for testharness.js that aren't expected to fail. Do we have some somewhere? |
(TaskCluster didn't pick up the moving from draft --> review, so close/open to kick it) |
Ping @jgraham :) |
(Sigh, and I forget again that GitHub isn't Gerrit, and doesn't update the commit description with the PR description. It's only slightly inaccurate - commit claims it doesn't port any tests but it actually changes two...) |
See web-platform-tests/rfcs#48 and
#21971.
Two tests are ported to the new methods to show their use.
Note that this PR does not remove the deprecated
assert_precondition
-that will be done in follow-up PRs.