Mobile/Testing/04 15 15: Difference between revisions
Jump to navigation
Jump to search
(→A Team) |
(→Round Table: - slight update) |
||
| Line 14: | Line 14: | ||
== Eideticker == | == Eideticker == | ||
= Round Table = | = Round Table = | ||
* [[https://elvis314.wordpress.com/2015/02/06/seta-search-for-extraneous-test-automation/ SETA]] | * [[https://elvis314.wordpress.com/2015/02/06/seta-search-for-extraneous-test-automation/ SETA]] should it come to android? | ||
** Now that desktop unittests are going live with SETA, we are looking into the future and see that 233/281 android jobs are not needed to catch all regressions on inbound/fx-team in the last 6 months. | ** Now that desktop unittests are going live with SETA, we are looking into the future and see that 233/281 android jobs are not needed to catch all regressions on inbound/fx-team in the last 6 months. | ||
** this would take some work from releng- but before we investigate we should see if it would be beneficial | |||
* reducing tp4m and tsvgx pagesets- a lot of duplicated pages (in results and patterns), we could cut the list in half to reduce time and still catch all changes in the last year. In addition this sets us up for a softer landing on getting the tests running on autophone due to the reduced runtime. | * reducing tp4m and tsvgx pagesets- a lot of duplicated pages (in results and patterns), we could cut the list in half to reduce time and still catch all changes in the last year. In addition this sets us up for a softer landing on getting the tests running on autophone due to the reduced runtime. | ||
= Action Items = | = Action Items = | ||
Revision as of 09:16, 15 April 2015
Previous Action Items
Status reports
Dev team
Rel Eng
Relops
A Team
- [gbrown] bug 1120727 Add mach commands for mochitest-plain and mochitest-chrome on Android
Autophone
Eideticker
Round Table
- [SETA] should it come to android?
- Now that desktop unittests are going live with SETA, we are looking into the future and see that 233/281 android jobs are not needed to catch all regressions on inbound/fx-team in the last 6 months.
- this would take some work from releng- but before we investigate we should see if it would be beneficial
- reducing tp4m and tsvgx pagesets- a lot of duplicated pages (in results and patterns), we could cut the list in half to reduce time and still catch all changes in the last year. In addition this sets us up for a softer landing on getting the tests running on autophone due to the reduced runtime.