Yocto 1.6 meta-intel testing plan: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
= Objectives = | |||
The test process is mainly focused to track and review the quality and performance of the meta-intel BSPs. | |||
=Test Areas = | |||
[https://wiki.yoctoproject.org/wiki/ | The meta-intel testing is being part of the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Target_System Target System] test are within Yocto 1.6 Overall Testing Plan. | ||
All the test cases that are being run can be found by accessing [[Testopia]] and browsing to the BSP component from it. Details on using Testopia, how to access the test runs and test cases is available in the [[Testopia]] wiki. | |||
target machines | The target machines tested are: | ||
* emenlow | * emenlow | ||
* crownbay | * crownbay | ||
| Line 13: | Line 15: | ||
* sugarbay | * sugarbay | ||
* crystalforest | * crystalforest | ||
= Test Cycle = | = Test Cycle = | ||
The testing of meta-intel BSPs is performed on every Full pass, Release Candidate or Release test according to the [[Yocto 1.6 Schedule]]. meta-intel BSPs are not covered in the weekly testing. | The testing of meta-intel BSPs is performed on every Full pass, Release Candidate or Release test according to the [[Yocto 1.6 Schedule]]. meta-intel BSPs are not covered in the weekly testing. | ||
Details on the Full Pass, Release Candidate or Release Test can be found in the Test Cycle section in the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Test_Cycle Yocto Overall 1.6 Test Plan] | Details on the Full Pass, Release Candidate or Release Test can be found in the Test Cycle section in the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Test_Cycle Yocto Overall 1.6 Test Plan]. In the [[Meta-intel Release Process]] is detailed the release process of meta-intel. | ||
= Test Automation = | = Test Automation = | ||
The plan for 1.6 HW automation is detailed in the HW automation bug [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1596 1596] | The plan for 1.6 HW automation is detailed in the HW automation bug [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1596 1596]. | ||
Revision as of 11:40, 4 December 2013
Objectives
The test process is mainly focused to track and review the quality and performance of the meta-intel BSPs.
Test Areas
The meta-intel testing is being part of the Target System test are within Yocto 1.6 Overall Testing Plan. All the test cases that are being run can be found by accessing Testopia and browsing to the BSP component from it. Details on using Testopia, how to access the test runs and test cases is available in the Testopia wiki.
The target machines tested are:
- emenlow
- crownbay
- fri2
- nuc
- jasperforest
- sugarbay
- crystalforest
Test Cycle
The testing of meta-intel BSPs is performed on every Full pass, Release Candidate or Release test according to the Yocto 1.6 Schedule. meta-intel BSPs are not covered in the weekly testing. Details on the Full Pass, Release Candidate or Release Test can be found in the Test Cycle section in the Yocto Overall 1.6 Test Plan. In the Meta-intel Release Process is detailed the release process of meta-intel.
Test Automation
The plan for 1.6 HW automation is detailed in the HW automation bug 1596.
