Yocto Project 2.2 Release Test Plan: Difference between revisions
From Yocto Project
Jump to navigationJump to search
| Line 89: | Line 89: | ||
= Test Deliverables = | = Test Deliverables = | ||
** Live Status [[2.2_QA_Status]] | |||
= Test Environment = | = Test Environment = | ||
Revision as of 12:45, 31 May 2016
Reversion history
| Version | Modifier | Comments |
|---|---|---|
| 1.0 | Jose Perez Carranza | First draft |
Introduction
This article is the overall test plan for version 2.2 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.2 Release
Owned features
As QA team we are also in charge for some features to implemetn/verify
To Verify 2.2_qa_owned_features_to_verify
To Implement 2.2_qa_owned_features
Bugs to Verify
Bugs that need verification form QA team 2.2_qa_owned_bugs
Test Items
| COMPONENT | TEMPLATES |
|---|---|
| ADT | |
| BSP | |
| CROPS | |
| Eclipse-Plugin | |
| Meta-Yocto | |
| Toaster | |
| eSDK | |
| OE-CORE / Bitbake | |
| Distro Testing | |
| Runtime (Compliance) | |
| Build Apliance | |
| pTest |
Features to be tested
Features to be tested are defined in component Test Plan QA_Master_Test_Plan#Component
Pass / Fail Criteria
This criteria is defined in Yocto_Project_v2.2_Status#Yocto_Project_v2.2_Release_Criteria
Exit Criteria
TBD
Test Deliverables
- Live Status 2.2_QA_Status
Test Environment
Schedule
Test Responsible
Execution History
| MILESTONE | REPORT |
|---|---|
| M1 | |
| M2 | |
| M3 | |
| M4 |
