Confirmed users
14,525
edits
QA/Loop/E2E: Difference between revisions
→Next Steps
(Created page with "= Summary = This page documents the test strategy of verifying Firefox Hello is working end-to-end. = Meetings = Discussions of end-to-end test coverage...") |
|||
| Line 62: | Line 62: | ||
= Next Steps = | = Next Steps = | ||
Anthony Hughes | |||
* document a list of what needs to be checked for each server/client/product deployment | |||
* develop a list of what needs to be automated for each server/client/product deployment | |||
* clarify roles, expectations, division of labour for Firefox OS | |||
* create a weekly status update page for Firefox OS | |||
* consider inviting Massimo Barone to the QA meeting | |||
* confirm with Shell what B2G 2.0/2.1 exist and whether they're Mozilla's to fix before Loop release | |||
* Find a Softvision resource to assist with test development | |||
* Syd Polk | Nils Ohlmeier | ||
* Review dmose's trello dashboard to make sure it’s a complete list of work to be completed | |||
Richard Pappalardo | |||
* | * Review dmose's trello dashboard to make sure it’s a complete list of work to be completed | ||
* Investigate feasibility of developing a middleware test using a fake Loop client to test server APIs | |||
Syd Polk | |||
* review and escalate gaps in current coverage to Anthony Hughes | |||
Tony Chung | |||
* Document on-going status of Firefox OS coverage | |||