QA/Mobile/FirefoxTVTestPlan: Difference between revisions

→‎Automated Tests: process update
(→‎Process: process change)
(→‎Automated Tests: process update)
Line 39: Line 39:


== Automated Tests ==
== Automated Tests ==
Automation tests will be mainly used for quick regression check of key UI features. Overall, automation tests will be added to the same Github repo, and executed locally for the time being (at this time there is no supported Android TV CI). While the unit tests will be run for each commit, UI Tests (in Espresso/UIAutomator framework) will be executed in master branch only.  The test result will be inspected for new failures, and github issue will be raised for tracking.
Automation tests will be mainly used for quick regression check of key UI features. Overall, automation tests will be added to the same Github repo, and executed on Firebase (For PRs) and Bitbar (For merge to master).  The test result will be inspected for new failures, and github issue will be raised for tracking.


Automation tests are located [https://github.com/mozilla-mobile/firefox-tv/tree/master/app/src/androidTest/java/org/mozilla/focus here].
Automation tests are located [https://github.com/mozilla-mobile/firefox-tv/tree/master/app/src/androidTest/java/org/mozilla/tv/firefox/ui here].


In addition to regularly run automated tests, QA will also generate screenshots for [https://pontoon.mozilla.org/projects/firefox-for-fire-tv/ l10n verification].
In addition to regularly run automated tests, QA will also generate screenshots for [https://pontoon.mozilla.org/projects/firefox-for-fire-tv/ l10n verification] upon request.


== Code Analysis ==
== Code Analysis ==
352

edits