New QA process

Given the new QA tooling (resulttool) available to manage QA test results and reporting, here was the proposed new QA process. First release to implement this process was 2.7_M3_ RC1.

The new QA process consists below:

Test Trigger
Test Planning 
Test Execution
Test Result Store
Test Monitoring & Reporting
Release Decision

Test Trigger: Each QA team will subscribe to QA notification email (request through Richard Purdie).

Test Planning: The lead QA team no longer need to setup Testopia and wiki page. Each QA team (eg. intel, windriver, etc) will perform planning on what extra tests they plan to run and when they'll send the results back, then send these planning information as acknowledge email to QA stakeholders (eg. Richard Purdie, Stephen Jolley) and the lead QA team. Each QA team can refer to OEQA for automated and manual test cases for their planning.

Test Execution: Each QA team will execute the planned extra tests. To make sure test result from the test execution could fully integrated to the new QA tooling (resulttool for test result management and reporting/regression), execute OEQA automated tests and OEQA manual tests through resulttool (refer https://wiki.yoctoproject.org/wiki/Resulttool#manualexecution).

Test Result Store: Each QA team will store test result to the remote yocto-testresults git repository using resulttool (refer https://wiki.yoctoproject.org/wiki/Resulttool#store), then send the QA completion email (include new defects information) to both QA stakeholder and the lead QA team.

Test Monitoring & Reporting: QA stakeholder will monitor testing progress from remote yocto-testresults git repository using resulttool (refer https://wiki.yoctoproject.org/wiki/Resulttool#report). Once every QA team completed the test execution, the lead QA team will create QA test report and regression using resulttool. Send email report to QA stakeholder and public yocto mailing list.

Release Decision: QA stakeholder will make the final decision for release.