Last Comment Bug 1170685 - [tracking bug] - port android talos tests to autophone
: [tracking bug] - port android talos tests to autophone
Status: RESOLVED FIXED
:
Product: Testing
Classification: Components
Component: Autophone (show other bugs)
: Trunk
: Unspecified Unspecified
-- normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
:
Mentors:
Depends on: 1216218 1172095 1172098 1172104 1172105 1172106 1172108 1172121 1178283 1183057 1188068 1192069 1214111 1214527 1214528 1214531 1216636
Blocks: 1182429 1186615
  Show dependency treegraph
 
Reported: 2015-06-02 11:44 PDT by Joel Maher ( :jmaher)
Modified: 2015-11-20 10:55 PST (History)
4 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
affected


Attachments

Description User image Joel Maher ( :jmaher) 2015-06-02 11:44:43 PDT
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
Comment 1 User image Joel Maher ( :jmaher) 2015-11-20 10:55:27 PST
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.

Note You need to log in before you can comment on or make changes to this bug.