QA: Difference between revisions
From Yocto Project
Jump to navigationJump to search
No edit summary |
|||
(28 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
==Current Release QA Trackers== | |||
*Bugs that need to be implemented by QA Team | |||
**[[2.2 qa assigned bugs]] | |||
** [[ | |||
* | *Bugs that need to be verified by QA Team | ||
** [[ | **[[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]] | **[[Old resolved bugs and features]] | ||
==Current Release QA Test Plans== | |||
* [[QA Master Test Plan]] | |||
* | * [[Yocto Project 2.2_Release Test Plan]] | ||
* [[2.2 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]] | |||
= QA | ==Current Release QA Test Cases== | ||
* | * [[Yocto 2.2 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 [[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]]. | |||
* | ==Reporting== | ||
**[[ | *[[Bug reporting and Information levels]] | ||
*[[Testopia]], the test manager | |||
*[[QA/Test_Reporting_Tool|The Test Reporting Tool]] | |||
*[http://errors.yoctoproject.org/Errors/ error report web] | |||
==Performance testing== | |||
[[Performance Test]] | |||
==QA Resources== | |||
*[[Rpm's Repository Setup for QA]] | |||
*[[Testopia]] | |||
*[[Testing Cycle]] | |||
*[[qa-tools|qa-tools Git Repository]] | |||
= Archive = | |||
You can find the previous QA work by release in the [[QA/Archive|Yocto Project QA Archive]]. | |||
= Other Relevant Data= | |||
* [[Yocto Bug Trend]] | * [[Yocto Bug Trend]] | ||
* Compliance Test Result | * Compliance Test Result | ||
Line 136: | Line 71: | ||
* [[Distribution Support]] | * [[Distribution Support]] | ||
* [[QA BKM sharing]] | * [[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]] | |||
[[Category:QA]] | [[Category:QA]] |
Revision as of 13:52, 15 August 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
- Performance Charts
- 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