QA: Difference between revisions
From Yocto Project
Jump to navigationJump to search
(5 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
==Current Release QA Trackers== | ==Current Release QA Trackers== | ||
* | *Bugs that need to be implemented by QA Team | ||
*[[2.2 qa | **[[2.2 qa assigned bugs]] | ||
*[[2.2 qa owned_bugs]] | *Bugs that need to be verified by QA Team | ||
*[[Old resolved bugs and features]] | **[[2.2 qa owned_bugs]] | ||
*Features to verify | |||
**[[2.2 qa_owned features to verify]] | |||
*Features to implement | |||
**[[2.2 qa owned features]] | |||
*Old Bugs | |||
**[[Old resolved bugs and features]] | |||
==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.2_Release Test Plan]] | ||
* [[2.2 QA Status]] | |||
* [[Toaster testing plan]] | * [[Toaster testing plan]] | ||
* [[eSDK | * [[Extensible SDK Test Plan (eSDK)]] | ||
* [[Distro Testing Plan]] | * [[Distro Testing Plan]] | ||
* [[BSP Test Plan]] | * [[BSP Test Plan]] | ||
==Current Release QA Test Cases== | ==Current Release QA Test Cases== | ||
* [[Yocto 2. | * [[Yocto 2.2 Test Cases]] | ||
==Test Automation== | ==Test Automation== | ||
Line 31: | Line 41: | ||
==Reporting== | ==Reporting== | ||
*[[Bug reporting and Information levels]] | *[[Bug reporting and Information levels]] | ||
*[[Testopia]] | *[[Testopia]], the test manager | ||
*[[QA/Test_Reporting_Tool|The Test Reporting Tool]] | |||
*[http://errors.yoctoproject.org/Errors/ error report web] | *[http://errors.yoctoproject.org/Errors/ error report web] | ||
Revision as of 22:37, 19 July 2016
Current Release QA Trackers
- Bugs that need to be implemented by QA Team
- Bugs that need to be verified by QA Team
- Features to verify
- Features to implement
- Old Bugs
Current Release QA Test Plans
- QA Master Test Plan
- Yocto Project 2.2_Release Test Plan
- 2.2 QA Status
- Toaster testing plan
- Extensible SDK Test Plan (eSDK)
- Distro Testing Plan
- BSP Test Plan
Current Release QA Test Cases
Test Automation
Autobuilder
The AutoBuilder is the automated 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
- Bug reporting and Information levels
- Testopia, the test manager
- The Test Reporting Tool
- error report web
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