QA: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(10 intermediate revisions by the same user not shown)
Line 2: Line 2:


*Bugs that need to be implemented by QA Team
*Bugs that need to be implemented by QA Team
**[[https://wiki.yoctoproject.org/wiki/2.3_QA_OWNED_BUGS | 2.2 qa assigned bugs]]
**[[2.3_QA_OWNED_BUGS | 2.3 QA Assigned Bugs]]


*Bugs that need to be verified by QA Team  
*Bugs that need to be verified by QA Team  
**[[2.2 qa owned_bugs]]
**[[2.3_QA_Bugs_To_Verify]]
 
<!--
*Features to verify  
*Features to verify  
**[[2.2 qa_owned features to verify]]
**[[2.2 qa_owned features to verify]]
Line 12: Line 12:
*Features to implement  
*Features to implement  
**[[2.2 qa owned features]]
**[[2.2 qa owned features]]
-->


*Old Bugs  
*Old Bugs that need to be Verified
**[[Old resolved bugs and features]]
**[[Old resolved bugs and features]]
*2.2 Test Run Templates
**[[Yocto_Project_2.3_Release_Test_Plan#Test_Items | Test Run Templates]]


==Current Release QA Test Plans==
==Current Release QA Test Plans==
* [[QA Master Test Plan]]
* [[QA Master Test Plan]]
* [[Yocto Project 2.2_Release Test Plan]]
* [[Yocto Project 2.3_Release Test Plan]]
* [[2.2 QA Status]]
* [[2.2 QA Status]]
* [https://wiki.yoctoproject.org/charts/perf_milestone_GDC/performance_test.html  Performance Charts ]
* [https://wiki.yoctoproject.org/charts/perf_milestone_GDC/performance_test.html  Performance Charts ]
Line 27: Line 31:


==Current Release QA Test Cases==
==Current Release QA Test Cases==
* [[Yocto 2.2 Test Cases]]
* [[Yocto 2.3 Test Cases]]


==Test Execution==
==Test Execution==

Revision as of 18:34, 21 November 2016

Current Release QA Trackers

Current Release QA Test Plans

Current Release QA Test Cases

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. (Partially working, feature in progress at request #9880)

Yocto Project QA heavily relies in the Autobuilder thanks to the aforementioned scheduled and on demand test execution features.

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 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. 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

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