QA: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(45 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Current Release QA Trackers==
== 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/.


*Test Plan
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:
**


*Live Status
Test Trigger
**
Test Planning
Test Execution
Test Result Store
Test Monitoring & Reporting
Release Decision


*Bugs that need to be implemented by QA Team
=== Test Trigger ===
**[[2.3_QA_OWNED_BUGS | 2.3 QA Assigned Bugs]]
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.


*Bugs that need to be verified by QA Team
=== Test Planning ===
**[[2.3_QA_Bugs_To_Verify]]
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.
<!--
*Features to verify
**[[2.2 qa_owned features to verify]]


*Features to implement
=== Test Execution ===
**[[2.2 qa owned features]]
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).  
-->


*Old Bugs that need to be Verified
=== Test Result Store ===
**[[Old resolved bugs and features]]
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.


*2.2 Test Run Templates
=== Test Result Repo ===
**[[Yocto_Project_2.3_Release_Test_Plan#Test_Items | Test Run Templates]]
 
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==
==Current Release QA Test Plans==
* [[QA Master Test Plan]]
 
* [[Yocto Project 2.3_Release Test Plan]]
* [[Yocto Project 3.4_Release Test Plan]]  
* [[2.3 QA Status]]
* [https://wiki.yoctoproject.org/charts/perf_milestone_GDC/performance_test.html  Performance Charts ]
* [[Toaster testing plan]]
* [[Extensible SDK Test Plan (eSDK)]]
* [[Distro Testing Plan]]
* [[BSP Test Plan]]
* [[BSP Test Plan]]
* [https://lists.yoctoproject.org/pipermail/yocto-perf/  Performance Archives ]


==Current Release QA Test Cases==
==Test Execution==  
* [[Yocto 2.3 Test Cases]]
 
==Test Execution==
===Autobuilder===
===Autobuilder===


Line 47: Line 60:
** That each image created executes the corresponding set of [[image tests|image/run-time tests]]
** 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]]
** Specific Autobuilder tasks for running [[oe-selftest|build-time testing]]
* A service for on demand testing requests. (Partially working, feature in progress at request [https://bugzilla.yoctoproject.org/show_bug.cgi?id=9080 #9880])
* A service for on demand testing requests.


Yocto Project QA heavily relies in the Autobuilder thanks to the aforementioned scheduled and on demand test execution features.
===Image Testing===
===Image Testing===
In order to execute tests in an image, it is necessary to boot it in either a virtual or a physical target.  
In order to execute tests in an image, it is necessary to boot it in either a virtual or a physical target.  
Line 62: Line 74:


# 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.
# 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 [http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#exporting-tests exporting tests] 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.
 
===Setting up Targets with Devauto===
 
Manual instructions for setting up the physical test targets appear in many parts of the Yocto Project documentation (i.e. [http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#building-an-image-for-hardware here]). It is easy to setup one target using those instructions but it becomes challenging for the cases where multiple targets have to be prepared or the case where it is required to serialize a changing setup over time, for one: testing on several images using the same target.
 
[[Devauto]] is the Python library and command line interface intended to manage the device automation assets that act upon the target's physical state. Refer to the [[Devauto]] documentation for more information about the hardware supported and the library and CLI functionality.


===Creating and Adding New Tests===
===Creating and Adding New Tests===
Line 78: Line 84:
==Reporting==
==Reporting==
*[[Bug reporting and Information levels]]
*[[Bug reporting and Information levels]]
*[[Testopia]], the test manager
*[[https://wiki.yoctoproject.org/wiki/Resulttool#report The Test Reporting Tool]]
*[[QA/Test_Reporting_Tool|The Test Reporting Tool]]
*[http://errors.yoctoproject.org/Errors/ error report web]  
*[http://errors.yoctoproject.org/Errors/ error report web]
*[[https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/ Test results report]]
*[[QA REPORT TEMPLATE | Wiki of QA Report Template]]


==Performance testing==
==Performance testing==
Line 87: Line 92:


==QA Resources==
==QA Resources==
*[[Rpm's Repository Setup for QA]]
*[[QA Master Test Plan]]  
*[[Testopia]]
*[[Resulttool]]  
*[[Testing Cycle]]
*[[https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults |qa results Git Repository]]
*[[qa-tools|qa-tools Git Repository]]
*[[https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib |qa results staging Git Repository]]


= Archive =
= Archive =
Line 102: Line 107:
** [[Posix result]]
** [[Posix result]]
** [[LSB Result]]
** [[LSB Result]]
* [[ADT Testing]]
* [[Regression Test]]
* [[Performance Test]]
* [[Distro Test]]
* [[Distribution Support]]
* [[Distribution Support]]
* [[QA BKM sharing]]
* [[LAVA server vs Yocto HW automation testing]]
* [[LAVA server vs Yocto HW automation testing]]
** Note: The LAVA framework usage stopped in favor of testing in the AutoBuilder in early 2016.
** Note: The LAVA framework usage stopped in favor of testing in the AutoBuilder in early 2016.


==List of Automated Tests==
==List of Automated Tests==
*[[Distribution Support‎]]
* [[Ptest]]
* add ptest wiki
* add piglit test wiki
* add piglit test wiki
* add kernel test wiki
* [[Kernel]]
*[[LSB]]
*[[LSB]]
*[[LSB Result]]
*[[LSB Result]]
Line 125: Line 124:
*[[POSIX History Results]]
*[[POSIX History Results]]
*[[Automated package upgrade testing]]
*[[Automated package upgrade testing]]
[[Category:QA]]

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

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:
  • 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:

  1. Boot the image in the target by following the building an image for hardware instructions.
  2. 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

Performance testing

Performance Test

QA Resources

Archive

You can find the previous QA work by release in the Yocto Project QA Archive.

Other Relevant Data

List of Automated Tests

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=QA&oldid=84917"