Closed
Bug 475778
Opened 15 years ago
Closed 11 years ago
integrate fennec automation code into existing automation
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Unassigned)
References
Details
We have developed a lot of tools to make the unittests run on Fennec. There are a lot of little tweaks necessary and many of them are useful for Firefox. I have outlined our toolset (maemkit): https://wiki.mozilla.org/Mobile/Fennec_Automation#Maemkit_Toolset More specifically, here are instructions for running the individual tests on Fennec: Mochitest: http://wiki.mozilla.org/Mobile/Fennec_Mochitest Chrome: http://wiki.mozilla.org/Mobile/Fennec_Chrome Reftest: http://wiki.mozilla.org/Mobile/Fennec_Reftests Bug 421611 is resolving a lot of the packaging issues which are required to get the tests onto the device. Some of the things which we have done to work smoother on Fennec: - run directories/manifests as a single chunk instead of everything at once - split up a directory/manifest to reduce the runtime of a given test chunk - run a subset of chunks on a given device to allow for parallel runs - read options from a config file The goal of this bug is to identify which pieces we will integrate into the existing automation and what pieces will remain in an external tool which we can check in.
Reporter | ||
Updated•15 years ago
|
Hahaha, wow this is an old bug. I'm gonna close this as fixed (even though it doesn't have a patch) cause we run fennec tests in automation all the dadgum time. Lots of patches landed to fix this. Nice work, us!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•