QA: Difference between revisions
No edit summary |
|||
| (124 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
== QA Process== | |||
=== Intro === | |||
The Yocto Project primarily runs QA through its autobuilder. Patches are pre-tested using the 'a-quick' builds on the project autobuilder https://autobuilder.yoctoproject.org/typhoon/#/console usually in master-next or ross/mut branches. XXX-next branches are also used for testing stable branch changes. We aim to only merge patches which pass these tests. A more comprehensive set of tests is available in 'a-full' builds which may also be used. Test results for all builds are saved in json format and can be handled by the 'resultool' script. Build ouput/results can be seen at https://autobuilder.yocto.io/pub/non-release/. | |||
For milestone and main project releases, an 'a-full' build is run as normal but the options to save build output, send a QA email and generate a release are selected. This then triggers a more extensive QA process where other teams can contribute to and extend the autobuilder results as follows: | |||
Test Trigger | |||
Test Planning | |||
Test Execution | |||
Test Result Store | |||
* | Test Monitoring & Reporting | ||
**[[Yocto | Release Decision | ||
=== Test Trigger === | |||
Each QA team can subscribe to QA notification email which is sent from the autobuilder (request through Richard Purdie) and also to the yocto mailing list. The list of notifications is maintained on config.json in the yocto-autobuilder-helper git repository which has a branch per release. | |||
* | === 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, Programme Management (Stephen Jolley) and Release Engineering), yocto mailing list 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-contrib 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 Repo === | |||
After testing is complete, lead QA team will upload test results and test report in yocto-testresults-contrib git repo (https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults) and send QA release mail. This is a staging repo where test results and test report are kept for tests run by independent test teams. | |||
* | To access test results, clone the repo https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/ and checkout QA branch "intel-yocto-testresults" | ||
* | For tests run at Autobuilder, test results and reports for release builds can be find at https://autobuilder.yocto.io/pub/releases/ inside release version folder. | ||
=== 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, 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. | |||
**[https:// | |||
=== Release Decision === | |||
QA stakeholder will make the final decision for release. | |||
Once decision is taken to release a milestone, RE team will take test results from staging repo and put in https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults/ git repo under same commit id as poky. | |||
==Current Release QA info== | |||
Tracking info for current release | |||
* For latest release info, go to https://autobuilder.yocto.io/pub/releases/ | |||
* For latest QA results, go to https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults | |||
==Current Release QA Test Plans== | |||
* [[Yocto Project 3.4_Release Test Plan]] | |||
* [[BSP Test Plan]] | |||
* [https://lists.yoctoproject.org/pipermail/yocto-perf/ Performance Archives ] | |||
==Test Execution== | |||
===Autobuilder=== | |||
The [[AutoBuilder]] is Yocto Project's tool for non-manual test execution, it performs the following functions: | |||
* A scheduled nightly build and test execution that includes: | |||
** That each image created executes the corresponding set of [[image tests|image/run-time tests]] | |||
** Specific Autobuilder tasks for running [[oe-selftest|build-time testing]] | |||
* A service for on demand testing requests. | |||
===Image Testing=== | |||
In order to execute tests in an image, it is necessary to boot it in either a virtual or a physical target. | |||
'''Testing Images in Virtual Targets''': | |||
The execution in a virtual environment has a nice flow, documented in the [[Image_tests#Enabling_and_running_the_tests|Image Tests Enabling...]] section. | |||
'''Testing Images in Physical Targets''': | |||
For executing tests in physical targets it would be required to: | |||
# Boot the image in the target by following the [http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#building-an-image-for-hardware building an image for hardware] instructions. | |||
# Run the image tests by following the [https://wiki.yoctoproject.org/wiki/BSP_Test_Plan#Automated_Tests image test] or [http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#exporting-tests exporting tests] instructions. | |||
===Creating and Adding New Tests=== | |||
Tests for a given component can be automated in the AutoBuilder. With that purpose, follow the [[AutoBuilder/Adding Automated Tests|Adding Automated Tests]] to the Autobuilder Guide. | |||
A list of tests that are automated [[QA#List_of_Automated_Tests|can be seen here]]. | |||
==Reporting== | |||
*[[Bug reporting and Information levels]] | |||
*[[https://wiki.yoctoproject.org/wiki/Resulttool#report The Test Reporting Tool]] | |||
*[http://errors.yoctoproject.org/Errors/ error report web] | |||
*[[https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/ Test results report]] | |||
==Performance testing== | |||
[[Performance Test]] | |||
==QA Resources== | |||
*[[QA Master Test Plan]] | |||
*[[Resulttool]] | |||
*[[https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults |qa results Git Repository]] | |||
*[[https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib |qa results staging Git Repository]] | |||
= Archive = | |||
You can find the previous QA work by release in the [[QA/Archive|Yocto Project QA Archive]]. | |||
= Other Relevant Data= | |||
* [[Yocto Bug Trend]] | * [[Yocto Bug Trend]] | ||
* Compliance Test Result | * Compliance Test Result | ||
| Line 40: | Line 107: | ||
** [[Posix result]] | ** [[Posix result]] | ||
** [[LSB Result]] | ** [[LSB Result]] | ||
* [[Distribution Support]] | * [[Distribution Support]] | ||
* [[ | * [[LAVA server vs Yocto HW automation testing]] | ||
* | ** Note: The LAVA framework usage stopped in favor of testing in the AutoBuilder in early 2016. | ||
[[ | ==List of Automated Tests== | ||
* [[Ptest]] | |||
* add piglit test wiki | |||
* [[Kernel]] | |||
*[[LSB]] | |||
*[[LSB Result]] | |||
*[[LTP]] | |||
*[[LTP result]] | |||
*[[POSIX]] | |||
*[[Posix result]] | |||
*[[POSIX-results]] | |||
*[[POSIX History Results]] | |||
*[[Automated package upgrade testing]] | |||
Latest revision as of 05:23, 8 September 2021
QA Process
Intro
The Yocto Project primarily runs QA through its autobuilder. Patches are pre-tested using the 'a-quick' builds on the project autobuilder https://autobuilder.yoctoproject.org/typhoon/#/console usually in master-next or ross/mut branches. XXX-next branches are also used for testing stable branch changes. We aim to only merge patches which pass these tests. A more comprehensive set of tests is available in 'a-full' builds which may also be used. Test results for all builds are saved in json format and can be handled by the 'resultool' script. Build ouput/results can be seen at https://autobuilder.yocto.io/pub/non-release/.
For milestone and main project releases, an 'a-full' build is run as normal but the options to save build output, send a QA email and generate a release are selected. This then triggers a more extensive QA process where other teams can contribute to and extend the autobuilder results as follows:
Test Trigger Test Planning Test Execution Test Result Store Test Monitoring & Reporting Release Decision
Test Trigger
Each QA team can subscribe to QA notification email which is sent from the autobuilder (request through Richard Purdie) and also to the yocto mailing list. The list of notifications is maintained on config.json in the yocto-autobuilder-helper git repository which has a branch per release.
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, Programme Management (Stephen Jolley) and Release Engineering), yocto mailing list 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-contrib 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 Repo
After testing is complete, lead QA team will upload test results and test report in yocto-testresults-contrib git repo (https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults) and send QA release mail. This is a staging repo where test results and test report are kept for tests run by independent test teams.
To access test results, clone the repo https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/ and checkout QA branch "intel-yocto-testresults"
For tests run at Autobuilder, test results and reports for release builds can be find at https://autobuilder.yocto.io/pub/releases/ inside release version folder.
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, 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
QA stakeholder will make the final decision for release. Once decision is taken to release a milestone, RE team will take test results from staging repo and put in https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults/ git repo under same commit id as poky.
Current Release QA info
Tracking info for current release
- For latest release info, go to https://autobuilder.yocto.io/pub/releases/
- For latest QA results, go to https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults
Current Release QA Test Plans
Test Execution
Autobuilder
The AutoBuilder is Yocto Project's tool for non-manual test execution, it performs the following functions:
- A scheduled nightly build and test execution that includes:
- That each image created executes the corresponding set of image/run-time tests
- Specific Autobuilder tasks for running build-time testing
- A service for on demand testing requests.
Image Testing
In order to execute tests in an image, it is necessary to boot it in either a virtual or a physical target.
Testing Images in Virtual Targets:
The execution in a virtual environment has a nice flow, documented in the Image Tests Enabling... section.
Testing Images in Physical Targets:
For executing tests in physical targets it would be required to:
- Boot the image in the target by following the building an image for hardware instructions.
- Run the image tests by following the image test or exporting tests instructions.
Creating and Adding New Tests
Tests for a given component can be automated in the AutoBuilder. With that purpose, follow the Adding Automated Tests to the Autobuilder Guide.
A list of tests that are automated can be seen here.
Reporting
- Bug reporting and Information levels
- [The Test Reporting Tool]
- error report web
- [Test results report]
Performance testing
QA Resources
Archive
You can find the previous QA work by release in the Yocto Project QA Archive.
Other Relevant Data
- Yocto Bug Trend
- Compliance Test Result
- Distribution Support
- LAVA server vs Yocto HW automation testing
- Note: The LAVA framework usage stopped in favor of testing in the AutoBuilder in early 2016.
List of Automated Tests
- Ptest
- add piglit test wiki
- Kernel
- LSB
- LSB Result
- LTP
- LTP result
- POSIX
- Posix result
- POSIX-results
- POSIX History Results
- Automated package upgrade testing
