Yocto Project 2.3 Release Test Plan
Reversion history
| Version | Modifier | Comments |
|---|---|---|
| 1.0 | Jose Perez Carranza | First draft |
References
Documents that support this test plan
Introduction
This test plan for Yocto Project 2.3 release supports the following objectives:
- To define the the tools to be used throughout the testing process.
- To communicate to the responsible parties the items to be tested, set expectations around schedule, and define environmental needs.
- To define how the tests will be conducted.
- Release Criteria
- Risks and contingencies
The overall test plan for version 2.3 of the Yocto Project, for all the generic information this document will be pointing QA Master Test Plan
Objectives
QA_Master_Test_Plan#Objectives_and_Tasks
Test Strategy
Is followed the general strategy defined on QA_Master_Test_Plan#Testing_Strategy and below is showed specific information applicable only for 2.3 Release
Bugs Tracking
- Bugs that need to be implemented by QA Team
- Bugs that need to be verified by QA Team
- Old Bugs that need to be Verified
Test Items
| Code of Colors |
|---|
| Active
Tracked on Testpoia |
| Active
Non Tracked on Testopia |
| In Design
Will be tracked on Tesopia |
| Inactive |
Test Cases
Features to be tested
All component to be tested on 2.3 are in #Test Items a detailed list of features per component can be found in Test Plan of the components QA_Master_Test_Plan#Component
Features pending to be tested
Here is a list of areas that are not yet covered and need some work, implement test cases and add it to a component that belongs or create a new test plan for new component.
- build-appliance - can we run builds in the build-appliance image?
- Verify if -c menuconfig work?
- Verify if -c devshell work?
- Verify if BBPOSTCONF and BBPRECONF work in bitbake?
- Verify if oe-pkgdata-util print help when no parameters specified?
- Verify if parsing time is improved with a hot codeparser cache (build metrics did catch a regression here but we had to manually spot it).
- Verify Bitbake sane error if a layer doesn't exist? (no backtrace?) send-error-report - no unittesting, only caught python3 issues when it failed to send errors
- Verify if buildhistory_analsysis.py is tested
- Verify if compression image types is tested
- Verify combo-layer
- Verify yocto-bsp/yocto-layer
- Verify oe-selftest coverage
- Verify bitbake -u depexp -g XXX
- rpm to be replaced
- <ADD MORE>
Pass / Fail Criteria
This criteria is defined in Yocto_Project_v2.3_Status#Yocto_Project_v2.3_Release_Criteria
Exit Criteria
As defined in QA_Master_Test_Plan#Entry and Exit Criteria
Test Deliverables
- Live Status 2.3_QA_Status
- Final execution Report #Execution History
- Mail sent to the mailing list
Test Environment
There are different environments and tools for every type of testing refer to QA_Master_Test_Plan#Test_Areas for more detailed information.
Schedule
The planed schedule for 2.3 can be found at Yocto_2.3_Schedule
Live Schedule
| MILESTONE | STARTED | FINISHED | STATUS |
|---|---|---|---|
| M1 | |||
| M2 | |||
| M3 | |||
| M4 | |||
Execution History
| MILESTONE | REPORT |
|---|---|
| M1 | |
| M2 | |
| M3 | |
| M4 | |
