Closed
Bug 842321
Opened 13 years ago
Closed 11 years ago
Test runner should make .xpi with tests and run from it.
Categories
(Add-on SDK Graveyard :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: irakli, Unassigned)
References
Details
At the moment `test/addons` are the right way to test, but that requires quite a boilerplate. We should just make fake add-on with test files and run each test as main module, so we get a same behavior as `test/addons` but don't necessary have to write package.json etc..
Priority: -- → P3
Comment 1•13 years ago
|
||
We are now half way here. Now, each test runs in its own loader as main module.
Comment 2•11 years ago
|
||
Hey Irakli, do you still want to do this one? based on a recent discussion on #jetpack in irc:
14:06:51 <•gozala> erikvold: I guess what I'm saying I want to do as much as possible on the sdk side
14:07:11 <•gozala> so node could just spawn a process and let the firefox process do what's neceserray
14:08:31 <•gozala> for example running each add-on as test is something we could do on the sdk side itself
Flags: needinfo?(rFobic)
Updated•11 years ago
|
Blocks: sdk-test-issues
| Reporter | ||
Comment 3•11 years ago
|
||
I think we can close this one & reopen if it will be necessary, but likely we end up going a different route.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(rFobic)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•