Closed
Bug 1170685
Opened 9 years ago
Closed 8 years ago
[tracking bug] - port android talos tests to autophone
Categories
(Testing Graveyard :: Autophone, defect)
Testing Graveyard
Autophone
Tracking
(firefox41 affected)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox41 | --- | affected |
People
(Reporter: jmaher, Unassigned)
References
Details
in order to move away from depending on panda boards we need to find a solution for Talos. this solution is autophone. Over the last few months we have reduced the talos tests we run on android due to not useful, redundant, or already implemented in autophone. Currently we have: * tp4m - pageloader w/7 pages * tsvgx - pageloader w/14 pages * tcheck2 - robocop test There are a few pieces here to figure out: * getting the pageloader into autophone * creating a similar script for s1s2 for tp4m/tsvgx * resolving the output of pageloader to be parseable by our runner script * upload the results to phonedash/treeherder * ensure the output of tcheck2 is compatible with autophone/phonedash/treeherder (this is currently coded into robocop- maybe we need to fix this in tree) * create/modify the robocop script to run tcheck2 * determine which devices to run * determine which branches/frequency to run * find a schedule to run the tests, and when to turn off the talos ones * ensure we have support for alerts and/or people looking at the results
Reporter | ||
Updated•9 years ago
|
Reporter | ||
Comment 1•8 years ago
|
||
there is no actionable work to do here. We need to purchase some nexus-6 devices and get it running in the production environment- that is outside the scope of this.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•