New QA process - Revision history

Yeoh, Ee Peng: /* Test Monitoring & Reporting */

2019-04-10T07:44:26Z

Test Monitoring & Reporting

← Older revision		Revision as of 07:44, 10 April 2019
Line 23:		Line 23:

	== Test Monitoring & Reporting ==		== 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.		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, then store the report and regression into https://wiki.yoctoproject.org/wiki/Main_Page. Send email report to QA stakeholder and public yocto mailing list.

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

Yeoh, Ee Peng at 04:13, 4 April 2019

2019-04-04T04:13:13Z

← Older revision		Revision as of 04:13, 4 April 2019
Line 1:		Line 1:
	== Intro ==		== Intro ==
	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~~.		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:		The new QA process consists below:

Yeoh, Ee Peng at 08:41, 3 April 2019

2019-04-03T08:41:20Z

← Older revision		Revision as of 08:41, 3 April 2019
Line 1:		Line 1:
			== Intro ==
	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.		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.

Yeoh, Ee Peng at 08:15, 3 April 2019

2019-04-03T08:15:20Z

← Older revision		Revision as of 08:15, 3 April 2019
Line 9:		Line 9:
	Release Decision		Release Decision

	Test Trigger: Each QA team will subscribe to QA notification email (request through Richard Purdie).		== Test Trigger ==
			Each QA team will subscribe to QA notification email (request through Richard Purdie). The list of notifications is maintained on config.json in the yocto- autobuilder-helper which has a branch per release.

	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 Planning ==
			Once received the QA notification email, 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 reply to the QA notification email with the planned extra tests and estimate of execution time to QA stakeholders (eg. Richard Purdie, Stephen Jolley), yocto mailing list and the lead QA team. Each QA team can refer to OEQA for automated and manual test cases for their planning. The lead QA team no longer need to setup Testopia and wiki page.

	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 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 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.		== 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.		== Release Decision ==
			QA stakeholder will make the final decision for release.

Sangeeta Jain at 03:51, 2 April 2019

2019-04-02T03:51:34Z

← Older revision		Revision as of 03:51, 2 April 2019
Line 1:		Line 1:
	Given the new QA tooling (resulttool) available to manage QA test results and reporting, here was the proposed 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:		The new QA process consists below:

Yeoh, Ee Peng: Created page with "Given the new QA tooling (resulttool) available to manage QA test results and reporting, here was the proposed new QA process. The new QA process consists below: Test Trigg..."

2019-04-02T03:44:20Z

Created page with "Given the new QA tooling (resulttool) available to manage QA test results and reporting, here was the proposed new QA process. The new QA process consists below: Test Trigg..."

New page

Given the new QA tooling (resulttool) available to manage QA test results and reporting, here was the proposed new QA process.

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.