QA: Difference between revisions
From Yocto Project
Jump to navigationJump to search
| Line 23: | Line 23: | ||
===Adding Automated Tests=== | ===Adding Automated Tests=== | ||
Tests for a given component can be automated in the AutoBuilder. | 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]]. | A list of tests that are automated [[QA#List_of_Automated_Tests|can be seen here]]. | ||
Revision as of 18:16, 15 June 2016
Current Release QA Trackers
- 2.1 QA Owned Features
- 2.1 qa owned bugs
- 2.1 qa owned features to verify
- Old resolved bugs and features
Current Release QA Test Plans
- Yocto 2.1 Overall Test Plan
- Toaster testing plan
- SDK Testing Plan
- Distro Testing Plan
- BSP Test Plan
- QA_Master_Test_Plan
Current Release QA Test Cases
Test Automation
Autobuilder
The AutoBuilder is the automatic build and test framework used by Yocto Project QA.
Adding Automated 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
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
- 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
