Closed Bug 852538 Opened 12 years ago Closed 10 years ago

Allow using the jetpack test harness from anywhere in m-c

Categories

(Add-on SDK Graveyard :: General, defect, P1)

Product:
Add-on SDK Graveyard
Component:
General
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: glind, Assigned: evold)

References

Details

Already, the m-c tests have a target for testing the SDK itself. However, as features are implemented as jetpacks (test pilot, for example, and there may be others, especially if the process is easier), it would be nice to run their tests as well. It would be nice to see something like cfx test built a little deeper into the makefiles.
Yeah so currently the way jetpack tests work is we just point cfx to the source directory and have it run those tests. Likely what we need to do is copy the tests somewhere during the build process (and have any other tests copied there too) and have cfx run from there. This is similar to how the other testing harnesses work. This may well require cfx changes though, likely bug 844268.
Depends on: 844268
Assignee: nobody → dtownsend+bugmail
Priority: -- → P1
Morphing the summary to make more sense.
Summary: decide process for testing bundled jetpack addons into mozilla-central tests → Allow using the jetpack test harness from anywhere in m-c
Depends on: 968331
Assignee: dtownsend+bugmail → nobody
Assignee: nobody → evold
Fixed by bug 1035512
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.