Open
Bug 1093954
Opened 10 years ago
Updated 2 years ago
Make mochitest assertions work in ContentTask.spawn functions
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
NEW
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: Gijs, Unassigned)
References
(Blocks 1 open bug)
Details
Bonus points for adding enough wrapping such that is/ok/isnot and other assertion functions on SimpleTest get forwarded back to the chrome process.
Flags: qe-verify-
Flags: in-testsuite+
Flags: firefox-backlog+
Comment 1•10 years ago
|
||
e10s test bugs block e10s, but not a particular milestone.
Blocks: e10s-tests
tracking-e10s:
--- → +
Comment 2•9 years ago
|
||
Does bug 1107609 do what you are asking for in this bug? I wound up using ContentTask.spawn in a test I wrote recently and it's super handy.
Reporter | ||
Comment 3•9 years ago
|
||
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #2) > Does bug 1107609 do what you are asking for in this bug? I wound up using > ContentTask.spawn in a test I wrote recently and it's super handy. Yes, though I guess we can repurpose this bug to cover making assertions work in content when using it?
Comment 4•9 years ago
|
||
It's your bug, do what you want. :)
Reporter | ||
Updated•9 years ago
|
Depends on: 1107609
Summary: e10s - Add generic wrapper around addFrameScript to allow eval'ing arbitrary JS in the content process from a mochitest-browser test → Make mochitest assertions work in ContentTask.spawn functions
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•