QA

New QA Process

• New_QA_process - add description here only, no need of separate link

Current Release QA Trackers

• Test Plan
  • Yocto Project 2.7_Release Test Plan --remove this section

• Live Status
  • 2.7 QA Status- no need

• QA Execution History
  • 2.7 qa run history

• Bugs that need to be implemented by QA Team
  • 2.7 QA Assigned Bugs

• Bugs that need to be verified by QA Team
  • 2.7_QA_Bugs_To_Verify

• Old Bugs that need to be Verified
  • Old resolved bugs and features

• 2.7 Test Run Templates
  • Test Run Templates

Current Release QA Test Plans

• QA Master Test Plan
• Yocto Project 2.7_Release Test Plan
• 2.7 QA Status
• Performance Charts
• Toaster testing plan
• Extensible SDK Test Plan (eSDK)
• Distro Testing Plan
• BSP Test Plan

Current Release QA Test Cases

• Yocto 2.7 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:
  • 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. (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 image test or 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

• Bug reporting and Information levels
• Testopia, the test manager
• The Test Reporting Tool
• error report web
• Wiki of QA Report Template

Performance testing

Performance Test

QA Resources

• Rpm's Repository Setup for QA
• Testopia
• Testing Cycle
• qa-tools Git Repository

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
  • LTP result
  • Posix result
  • LSB Result
• ADT Testing
• Regression Test
• Performance Test
• Distro Test
• Distribution Support
• QA BKM sharing
• 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

• Distribution Support‎
• add ptest wiki
• add piglit test wiki
• add kernel test wiki
• LSB
• LSB Result
• LTP
• LTP result
• POSIX
• Posix result
• POSIX-results
• POSIX History Results
• Automated package upgrade testing