Closed Bug 809143 Opened 7 years ago Closed Last year

Get Jetpack tests running on automated Fennec test infrastructure

Categories

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

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: KWierso, Unassigned)

References

Details

Jetpack's support of Fennec is getting to the point where we should start getting automated tests running, to make sure we don't regress anything.

I'm not entirely sure what getting this all set up would entail, as I haven't really attempted much manual testing with Android. Matteo would probably know more.
I think for starters, setting up tests on the Jetpack tree for "Android 2.2 Armv6 opt" and for "Android 2.2 opt" would be sufficient, though getting the debug versions tested too would be better.
Is there any progress about it? We can't really claims that Mobile is supported by SDK until we don't have the automated tests properly running on Tinderbox. At the moment we'll continue to have the Mobile support as "experimental", but we should leave this status sooner rather than later.
Assignee: nobody → jsantell
Unassigning myself from bugs I haven't gotten around to
Assignee: jsantell → nobody
Summary: Get Jetpack tests running on Fennec in the test infrastructure → Get Jetpack tests running on automated Fennec test infrastructure
Severity: normal → critical
What would it take to enable the mochi-jp suite for Fennec?
Flags: needinfo?(dtownsend)
(In reply to Erik Vold [:erikvold] (please needinfo? me) from comment #4)
> What would it take to enable the mochi-jp suite for Fennec?

It's been so long since I looked at this that I'm afraid I don't know anymore. I could guess that the harness JS would need some changes as would runtests.py but that's probably not helpful.
Flags: needinfo?(dtownsend)
Priority: P1 → --
Add-on SDK is no longer supported so resolving bugs as INCOMPLETE
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.