Closed
Bug 1448492
Opened 6 years ago
Closed 6 years ago
[wpt-sync] Sync PR 10164 - Special-case idlharness.js errors as an assert_throw option
Categories
(Testing :: web-platform-tests, defect, P4)
Testing
web-platform-tests
Tracking
(firefox61 fixed)
RESOLVED
FIXED
mozilla61
Tracking | Status | |
---|---|---|
firefox61 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream error])
Sync web-platform-tests PR 10164 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/w3c/web-platform-tests/pull/10164 Details from upstream follow. Luke Bjerring <lukebjerring@google.com> wrote: > Special-case idlharness.js errors as an assert_throw option > > Fixes https://github.com/w3c/web-platform-tests/issues/10162 > > This adds support for more succinctly asserting behaviour of `idlharness.js` itself, using the same mechanism in `testharness.js`, e.g. when testing expected errors in `IdlArray.test()`. > > >
Reporter | ||
Updated•6 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/6f3e57f64d7d [wpt PR 10164] - Special-case idlharness.js errors as an assert_throw option, a=testonly
Comment 2•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/6f3e57f64d7d
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox61:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
You need to log in
before you can comment on or make changes to this bug.
Description
•