Yocto 1.5 Overall Test Plan: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(31 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Reversion history =
= Reversion history =
{|class="wikitable"
{|class="wikitable"
| Version || Modifier || Comments
! Version || Modifier || Comments
|-
|-
| 1.0 || Alexandru Georgescu || Initial Version  
| 1.0 || Alexandru Georgescu || Initial Version  
|-
| 2.0 || Mihai Lindner || RFC Version
|}
|}


= Introduction =
= Introduction =
This test plan defines test targets/components, scope, strategy, configurations as well as test execution cycles for 1.5 version of Yocto.
This article is the overall test plan for version 1.5 of the {{ns:4}}.
It contains an overview of the testing process, such as testing areas, types, cycles and reports, along with a summary and objective for each of the conducted validation activities.
Further on, sections may be linked to other articles that contain further details or information related to them.
Note that the information provided in this article, or articles linked here, is subject to changes when needed as to reflect the actual activities held for the current version of the {{ns:4}}.


=== Targets / Components to Be Tested ===
= Objectives =
The test process is mainly focused to track and review the quality and performance of the {{ns:4}}, along with its reference system and internal projects.
The plan also includes identifying and tracking areas subject to improvement, regression, validation of enhancements and bugs, development of testing methods with emphasis on automated testing.
Documentation and licensing status is not included in the scope of the testing process, unless otherwise noted e.g. as part of the process of verifying new features.


= Test Areas =
Each internal project, under {{ns:4}}, is an area subject to a testing process. Areas are grouped by the nature of their functionality, as follows:


* Core build system: includes build system tests also using additional features and tweaks for it.
== Build System ==
* Hob2: It includes functional tests for both frontend and backend of Hob2.
The build engine and the surrounding components, that provide the means to build an image or bake a bit of software. In this area the ''build-time'' tests are executed.
* Yocto ADT: It includes cross-toolchain, Eclipse plugin tests.
* BSPs: The core OS feature included Yocto kernel, distribution components(like connman, smart updater & zypper), file system.
* Performance: Checks the CPU power behavior by software level tool, such as '''powertop'''. Real Power consumption when idle is collected. The performance of the build system is also recorded.
* Distribution support: Current versions for supported distributions are tested along with one previous version and the beta release for the next one (the supported distributions are Ubuntu, Fedora, CentOS and OpenSUSE).
* Compliance testing: LSB, LTP and POSIX tests are ran on the the selected targets.
* Stress testing: Helltest + Crashme test suites are ran.


=== What will not be tested in Yocto v1.5 ===                                                                                                                                                                          
=== BitBake ===
Following feature categories won't be tested by QA team in Yocto v1.5:
Functional testing of BitBake, as a build engine, with all its features and components, against various configuration and scenarios.
* Documentation: QA will not validate the correctness of each documentation.
* License file: license files and legal process are owned by Distro team.


=== Test Environment ===
=== HOB ===
==== Test Platform matrix ====
Functional and usability testing of HOB as a graphical user interface for BitBake.


The following matrix represents the target images that will be validated in QA Test in 1.5.
=== Metadata ===
Testing the core metadata of the {{ns:4}} is mainly covered in the overall testing process, through other [[#Test Areas]] like [[#BitBake]] and [[#HOB]] mentioned above.


{| class="wikitable"
=== Build Performance ===
!colspan="6"|Target machines
The performance of the build system is tracked, with regards to time spent on passing through a build process, in multiple, commonly used, configurations.
|-
; Tool: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/contrib/build-perf-test.sh
|'''meta'''
; Results page: [[Performance Test]]
|'''meta-yocto-bsp'''
|'''meta-intel'''
|-
|qemuarm
|atom-pc
|emenlow
|-
|qemumips
|beagleboard
|crownbay
|-
|qemuppc
|mpc8315e-rdb
|fri2
|-
|qemux86
|routerstationpro
|nuc
|-
|qemux86-64
|
|jasperforest
|-
|
|
|sugarbay
|-
|}
 
 
The following list represents the list with all the platforms available for Yocto 1.5
 
{| class="wikitable"
|-
|'''Category'''
|! colspan="5" | '''QEMU'''
|! colspan="4" | '''Atom'''
|! colspan="3" | '''Core i7'''
| '''Xeon'''
| '''ARM HW'''
| ! colspan="2" | '''PPC HW'''
| '''MIPS HW'''
|-
|'''Platform'''
|
|
|
|
|
| atom-pc generic
| FRI2
| Cronwbay
| eMenlow
| Sugarbay
| Chiefriver
| HuronRiver
| JasperForest
| Beagleboard
| mpc8315e-rdb
| p1022ds
| routerstationpro
|-
|'''Arch'''
|x86
|x86_64
|arm
|ppc
|mips
|x86
|x86
|x86
|x86
|x86_64
|x86_64
|x86_64
|x86_64
|arm
|ppc
|ppc
|mips
|-
|'''Sato-SDK image'''
|yes
|yes
|yes
|yes
|yes
|yes
|yes
|yes
|yes
|yes
|yes
|yes
|
|
|yes
|yes
|yes
|-
|'''LSB-SDK image'''
|
|
|
|
|
|
|
|
|
|
|
|yes
|yes
|
|yes
|
|
|}
 
 
Notes:  
* Fullpass testing defined in execution plan will be performed against sato-sdk image.
* The atom images are both emgd and no-emgd images
 
=== Test Strategy and Approach ===
QA will cover following tests for each target in each round fullpass testing.


== Target System ==
Area focused on a target operating system or an application that comes with it, as the output of a build process. In this area the ''run-time'' tests are executed.


 
{|class="wikitable" style="text-align: center;"
The following matrix represents the Yocto Project components mapped by the test areas and by the Weekly and Full pass test levels.
| Machine type
 
!Target machine
{| class="wikitable"
|-
!colspan="4"|Test Areas
|-
|
|
|'''Components'''
! System Testing || [[#Compliance Testing]] || [[#Stress Testing]] || [[#System Performance]] || [[#Application Development Toolkit]]
|'''Weekly'''
|'''Full Pass'''
|-
!rowspan="4"|Build System
!Bitbake !! Yes* !! Yes
|-
!Build performance !! Yes* !! Yes
|-
!Metadata !! Yes* !! Yes
|-
!Distribution  !! Yes* !! Yes
|-
!rowspan="6"|Target
!Build Appliance !!  !! Yes
|-
|-
!QEMU images !! Yes* !! Yes
| rowspan="6" | [[#QEMU Machine]]
|-
|-
!BSP images  !! Yes* !! Yes
! qemuarm
| || yes || || || || yes
|-
|-
!Stress !! Yes* !! Yes
! qemumips
| || yes || || || || yes
|-
|-
!Target performance  !! Yes* !! Yes
! qemuppc
| || yes || || || || yes
|-
|-
!Compliance !!  !! Yes
! qemux86
| || yes || || || || yes
|-
|-
!rowspan="6"|Tools
! qemux86-64
!Eclipse !! Yes* !! Yes
| || yes || || || yes || yes
|-
|-
!ADT !! Yes* !! Yes
| rowspan="5" | [[#BSP Machine]]
|-
|-
!Autobuilder !! Yes* !! Yes
! atom-pc
|}
| || yes || || || ||
 
 
 
Note:
* On weekly test, the basic BSP will be covered: Atom-PC, Beagleboard, Routerstationpro, MPC8315e-rdb, P1022ds-rdb, and all the QEMU images (arm, x86, x86_64, ppc, mips)
* as mentioned in the Weekly test section, the weekly tests will cover the basic functionalities of the component.
* Compliance Test on Beagleboard and routerstation will only cover LTP and POSIX Test, since LSB test suite does not support ARM and MIPS.
* Jasperforest is selected for stress test, because it is powerful with 12 CPUs and 2GB memory. Moreover, it is a server, which needs more stress tests.
 
The following matrix represents Full pass and Weekly coverage of BSP testing.
 
{| class="wikitable" style=" color: green;"
|-
|-
! Test levels !!  Atom-PC !!  NUC !! Emenlow !! Sugarbay !! Jasperforest !! Crownbay !! FRI2 !! Beagleboard !! RouterstationPro !! MPC8315e-rdb !! P1022ds-rdb
! beagleboard
| || yes || yes || yes || ||
|-
|-
! Weekly !! Yes !!  !!  !!  !!  !!  !!  !! Yes !! Yes !! Yes !! Yes
! mpc8315e-rdb
| || yes || yes || || ||
|-
|-
! Full Pass !! Yes !! Yes !! Yes !! Yes !! Yes !! Yes !! Yes !! Yes !! Yes !! Yes !! Yes
! routerstationpro
| || yes || yes || || ||
|}
|}


= Test Areas =
The testing areas are defined by the {{ns:4}} component covered, and grouped by the components nature and destination, as follows:
== Build System ==
Including the build engine and the surrounding components, that provide the means to build an image or bake a bit of software. In this area the ''build-time'' tests are executed.
=== BitBake ===
Functional testing of BitBake, as a build engine, with all its features and components, against various configuration and scenarios.
=== HOB ===
Functional and usability testing of HOB as a graphical user interface for BitBake.
=== Metadata ===
Testing the core metadata of the {{ns:4}} is mainly covered in the overall testing process, of other [[#Test Area]]s like [[#BitBake]] and [[#HOB]] mentioned above.
=== Build Performance ===
The performance of the build system is tracked, with regards to time spent on passing through a build process, in multiple, commonly used, configurations.
; Tool: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/contrib/build-perf-test.sh
; Results page: [[Performance Test]]
== Target System ==
Area focused on a target operating system or an application that comes with it, as the output of a build process. In this area the ''run-time'' tests are executed.


=== QEMU Image ===
=== QEMU Machine ===
Covering all core, QEMU, machine definitions:
Covering all core, QEMU, machine definitions:
* qemuarm
* qemuarm
Line 256: Line 89:
* qemux86-64
* qemux86-64


=== BSP Image ===
=== BSP Machine ===
Covering BSPs included in the {{ns:4}}:
Covering BSPs included in the {{ns:4}}:
* atom-pc
* atom-pc
Line 262: Line 95:
* mpc8315e-rdb
* mpc8315e-rdb
* routerstationpro
* routerstationpro
Atom-PC, Beagleboard, RouterstationPro, MPC8315e-rdb, P1022ds-rdb, QEMU (arm, ppc, mips, x86, x86_64). The images tested will be core-image-sato-sdk.
The scope of BSP testing is to make sure that the core BSPs have basic functionality, like described below:
*Boot Test: Check if Yocto image is bootable with the bootloader.
*Installation/SW Update Test: Validate the Yocto image installation on hardware platform and software install/removal functions from the end users' perspective. Using zypper/rpm/SMART updater for software updates with hardisk installed image.
*Common system usage Test: shutdown/restart, suspend/resume, init 3/5 boot.
Component Test (aka. Feature Test): Based on sato image features to test. For example:
*Perl
*Rootless X
*Opening 3rd party application
*Code compiling and building binaries on the *-sdk images
*Continuous system updates analysis
(Basic functionality for tested features will be exercised as well as new functionality added in each release.)


=== Compliance Testing ===
=== Compliance Testing ===
Line 291: Line 109:


=== System Performance ===
=== System Performance ===
*; Objective:
**Track the run-time performance of targeted systems;


The run-time performance metrics will be measured using the following methods:
*; Indicators:
 
** Boot time for <tt>systemd</tt> and <tt>sysvinit</tt>;
* measure boot time for SystemD and SysVinit features
** Image size from [[Buildhistory]] to track regression;
* record image size from buildhistory to track regression
** Piglit test suite results;
* use Phoronix Test Suite tests to benchmark Yocto images
* run Piglit test suite


== Developer Tools ==
== Developer Tools ==
Line 322: Line 140:


== Distribution Support ==
== Distribution Support ==
The most recent previous version of one of the 4 supported distributions '''Ubuntu''', '''Fedora''', '''CentOS''', '''OpenSUSE''', and the latest beta version of those are the target for these tests.
; Criteria: The OS distribution version is still maintained at the time of the {{ns:4}} release (1.5 release date is: Oct. 18, 2013)
Basic functionalities of ADT, toolchaion, HOB2 and Core Build System ar testested on these targets.
; Coverage: Following a table with targeted distribution and versions:
 
{| class="wikitable"
The following coverage matrix will reprezent the supported distributions:
! Distro !! Version !! Release !! EOL
 
|-
{| class="wikitable" style=" color: green;"
| rowspan="4" | Ubuntu
|-
| 12.04.2 LTS || February 14, 2013 || April 2017
|-
| 12.10 || October 18, 2012 || April 2014
|-
| 13.04 || April 25, 2013 || January 2014
|-
| rowspan="4" | Fedora
|-
| 17 || May 29, 2012 || ~August 02, 2013
|-
| 18 || January 15, 2013 || ~December 12, 2013
|-
| 19 || July 2013 || ~
|-
| rowspan="3" | CentOS
|-
| 5 || ~ || March 31, 2017
|-
| 6 || ~ || November 30, 2020
|-
| rowspan="3" | Debian
|-
| 6 || February 6th, 2011 || obsolete
|-
|-
! Distribution
| 7 || May 4th, 2013 || current
! colspan="2" | '''Ubuntu'''
! colspan="2" | '''Fedora'''
! colspan="2" | '''CentOS'''
! colspan="2" | '''OpenSUSE'''
|-
|-
| '''Version''' || 13.04 || 13.10 || 18 || 19 || 6.3 || 6.4 || 12.3 || 13.1
| rowspan="3" | openSUSE
|-
|-
| '''RC Supported''' || Yes || || Yes || || Yes || || Yes ||
| 12.2 || October 22, 2012 || ~
|-
|-
| '''1.5 Supported''' || Yes || Yes || Yes || Yes || Yes || Yes || Yes || Yes
| 12.3 || May 28, 2013 || ~
|}
|}


Line 346: Line 184:
* List of all [[Test Cases]], included in a cycle or not.
* List of all [[Test Cases]], included in a cycle or not.


{|class="wikitable"
{|class="wikitable" style="text-align: center;"
| ||
| ||
!colspan="4"|Test execution cycle
!colspan="4"|Test execution cycle
Line 353: Line 191:
! [[#Sanity Test]] || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
! [[#Sanity Test]] || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
|-
! rowspan="4" |Build type  
! rowspan="5" |Build type  
|-
! Daily (M.U.T.)
! Daily (M.U.T.)
| yes || || ||
| yes || || ||
|-
|-
! Weekly build
! Weekly
| yes || yes || ||
| yes || yes || ||
|-
|-
! RC build
! Release Candidate
| yes || yes || yes ||
| yes || yes || yes ||
|-
|-
! Release
! Release
| yes || yes || yes || yes
| yes || yes || yes || yes
|-
! rowspan="11" | [[#Test Areas]]
! [[#BitBake]]
| yes || yes || yes ||
|-
! [[#HOB]]
| || yes || yes ||
|-
! [[#Build Performance]]
| || yes || ||
|-
! [[#QEMU Image]]
| yes || yes || yes ||
|-
! [[#BSP Image]]
| || yes || yes ||
|-
! [[#Compliance Testing]]
| || || || yes
|-
! [[#Stress Testing]]
| || || || yes
|-
! [[#System Performance]]
| || || || yes
|-
! [[#Application Development Toolkit]]
| || yes || yes ||
|-
! [[#Eclipse IDE Plugin]]
| || yes || yes || yes
|-
! [[#Build Appliance]]
| || || yes ||
|-
! rowspan="10" | Target machine
|-
! qemuarm
| yes || yes || yes ||
|-
! qemumips
| yes || yes || yes ||
|-
! qemuppc
| yes || yes || yes ||
|-
! qemux86
| yes || yes || yes ||
|-
! qemux86-64
| yes || yes || yes ||
|-
! atom-pc
| || yes || yes ||
|-
! beagleboard
| || yes || yes || yes
|-
! mpc8315e-rdb
| || yes || yes ||
|-
! routerstationpro
| || yes || yes || yes
|-
! rowspan="6" | Target image
|-
! core-image-sato
| yes || || ||
|-
! core-image-sato-dev
| yes || || ||
|-
! core-image-sato-sdk
| yes || yes || yes || yes
|-
! core-image-minimal
| yes || || ||
|-
! core-image-minimal-dev
| yes || || ||
|}
|}


== Sanity Test ==
== Sanity Test ==
Line 374: Line 294:


*; Objective:
*; Objective:
** Ensure the build output is sane / as expected;
** Build finished with no errors;
** Check basic QEMU image functionality, e.g. boot, network, package manager, etc.;
** Check basic QEMU image functionality, e.g. boot, network, package manager, etc.;
** Establish if testing cycle can continue, depending on the build type.
** Establish if testing cycle can continue, depending on the build type.
Line 390: Line 310:
*; Scope:
*; Scope:
** Images built as candidates for milestone or final release;
** Images built as candidates for milestone or final release;
** Passed [[#Sanity Test]]
** Passed [[#Weekly Test]]
** Passed [[#Weekly Test]]


Line 412: Line 331:
*; Objectives:
*; Objectives:
** Reduce effort with manual testing, by automating current tests;
** Reduce effort with manual testing, by automating current tests;
** Improve build-time and run-time testing.
** Improve run-time testing.


*; Tools:
*; Tools:
Line 436: Line 355:
** [[Yocto Project v1.5 Status#Feature/Task Board]]
** [[Yocto Project v1.5 Status#Feature/Task Board]]


= Test report =
= Test Report =
* [[1.5 QA Status]] will show a live status of currently active test runs;
*; Objectives:
* When a test cycle is complete, an email containing the test report is sent to the {{ns:4}} [https://lists.yoctoproject.org/listinfo/yocto mailing list];
** Show a live [[1.5 QA Status]] of the active test runs, on the latest build;
* [[1.5 qa run history]] contains previous test reports;
** Send out an report email to the {{ns:4}} [https://lists.yoctoproject.org/listinfo/yocto mailing list] at the end of a test cycle;
* [[QA Status TEMPLATE]] is used for reports;
** Archive reports at [[1.5 qa run history]];
* [[Testopia]] is used for test case management and reporting.
** Use [[QA Status TEMPLATE]] for reporting;
** Use [[Testopia]] as a tool for reporting;

Latest revision as of 13:03, 2 July 2013

Reversion history

Version Modifier Comments
1.0 Alexandru Georgescu Initial Version
2.0 Mihai Lindner RFC Version

Introduction

This article is the overall test plan for version 1.5 of the Yocto Project. It contains an overview of the testing process, such as testing areas, types, cycles and reports, along with a summary and objective for each of the conducted validation activities. Further on, sections may be linked to other articles that contain further details or information related to them. Note that the information provided in this article, or articles linked here, is subject to changes when needed as to reflect the actual activities held for the current version of the Yocto Project.

Objectives

The test process is mainly focused to track and review the quality and performance of the Yocto Project, along with its reference system and internal projects. The plan also includes identifying and tracking areas subject to improvement, regression, validation of enhancements and bugs, development of testing methods with emphasis on automated testing. Documentation and licensing status is not included in the scope of the testing process, unless otherwise noted e.g. as part of the process of verifying new features.

Test Areas

Each internal project, under Yocto Project, is an area subject to a testing process. Areas are grouped by the nature of their functionality, as follows:

Build System

The build engine and the surrounding components, that provide the means to build an image or bake a bit of software. In this area the build-time tests are executed.

BitBake

Functional testing of BitBake, as a build engine, with all its features and components, against various configuration and scenarios.

HOB

Functional and usability testing of HOB as a graphical user interface for BitBake.

Metadata

Testing the core metadata of the Yocto Project is mainly covered in the overall testing process, through other #Test Areas like #BitBake and #HOB mentioned above.

Build Performance

The performance of the build system is tracked, with regards to time spent on passing through a build process, in multiple, commonly used, configurations.

Tool
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/contrib/build-perf-test.sh
Results page
Performance Test

Target System

Area focused on a target operating system or an application that comes with it, as the output of a build process. In this area the run-time tests are executed.

Machine type Target machine System Testing #Compliance Testing #Stress Testing #System Performance #Application Development Toolkit
#QEMU Machine
qemuarm yes yes
qemumips yes yes
qemuppc yes yes
qemux86 yes yes
qemux86-64 yes yes yes
#BSP Machine
atom-pc yes
beagleboard yes yes yes
mpc8315e-rdb yes yes
routerstationpro yes yes


QEMU Machine

Covering all core, QEMU, machine definitions:

  • qemuarm
  • qemumips
  • qemuppc
  • qemux86
  • qemux86-64

BSP Machine

Covering BSPs included in the Yocto Project:

  • atom-pc
  • beagleboard
  • mpc8315e-rdb
  • routerstationpro

Compliance Testing

Compliance test suites / frameworks used:

  • LSB tests
  • POSIX tests
  • LTP tests

Stress Testing

Stress tests are run on Beagleboard and Jasperforest BSPs. Details as follow:

  • Beagleboard core-image-sato-sdk image is tested using LTP and Crashme stress tests
  • Jasperforest core-image-lsb-sdk image is tested using Helltest and Crashme stress tests

System Performance

  • Objective
    • Track the run-time performance of targeted systems;
  • Indicators
    • Boot time for systemd and sysvinit;
    • Image size from Buildhistory to track regression;
    • Piglit test suite results;

Developer Tools

Application Development Toolkit

ADT testing includes tests for ADT-installer, meta-toolchain-sdk and user build sdk. It will be covered in Weekly and Fullpass testing.

  • Cross-toolchain install&compiling Test
  • relocatable SDK
  • ADT installer
  • toolchain tarballs
  • yocto build tree

Eclipse IDE Plugin

Eclipse plugin tests will cover the basic functionalities. This includes installation, configuring Yocto Project ADT settings, Yocto BSP, Bitbake project and project compiling and deployment to the target. Based on the features that will be implemented, new test cases will be added, to support Windows and Mac support. This will be more detailed in the Features section.

  • headless build
  • C/C++ project creation
  • debug/deploy
  • user space tools
  • Bitbake project

Build Appliance

The basic functionality of the Build appliance will be tested. The tests consists on building successfully a build-appliance-image, launch HOB.

Distribution Support

Criteria
The OS distribution version is still maintained at the time of the Yocto Project release (1.5 release date is: Oct. 18, 2013)
Coverage
Following a table with targeted distribution and versions:
Distro Version Release EOL
Ubuntu
12.04.2 LTS February 14, 2013 April 2017
12.10 October 18, 2012 April 2014
13.04 April 25, 2013 January 2014
Fedora
17 May 29, 2012 ~August 02, 2013
18 January 15, 2013 ~December 12, 2013
19 July 2013 ~
CentOS
5 ~ March 31, 2017
6 ~ November 30, 2020
Debian
6 February 6th, 2011 obsolete
7 May 4th, 2013 current
openSUSE
12.2 October 22, 2012 ~
12.3 May 28, 2013 ~

Test Cycle

Test execution cycle
#Sanity Test #Weekly Test #Full Pass Test #Release Test
Build type
Daily (M.U.T.) yes
Weekly yes yes
Release Candidate yes yes yes
Release yes yes yes yes
#Test Areas #BitBake yes yes yes
#HOB yes yes
#Build Performance yes
#QEMU Image yes yes yes
#BSP Image yes yes
#Compliance Testing yes
#Stress Testing yes
#System Performance yes
#Application Development Toolkit yes yes
#Eclipse IDE Plugin yes yes yes
#Build Appliance yes
Target machine
qemuarm yes yes yes
qemumips yes yes yes
qemuppc yes yes yes
qemux86 yes yes yes
qemux86-64 yes yes yes
atom-pc yes yes
beagleboard yes yes yes
mpc8315e-rdb yes yes
routerstationpro yes yes yes
Target image
core-image-sato yes
core-image-sato-dev yes
core-image-sato-sdk yes yes yes yes
core-image-minimal yes
core-image-minimal-dev yes


Sanity Test

Brief and quick automated tests, with execution time of maximum 10 minutes.

  • Objective
    • Build finished with no errors;
    • Check basic QEMU image functionality, e.g. boot, network, package manager, etc.;
    • Establish if testing cycle can continue, depending on the build type.

Weekly Test

  • Scope
    • Images built weekly and released through the distribution team.
    • Passed #Sanity Test
  • Objective
    • Functionality test on most areas with minimum sets of tests;
    • Regression test with high probability to find bugs.

Full Pass Test

  • Scope
    • Images built as candidates for milestone or final release;
    • Passed #Weekly Test
  • Objective
    • Ensure functionality of all Yocto Project components.

Release Test

  • Objective
    • All scheduled features are covered, or rescheduled;
    • All relevant bugs are fixed and verified.
  • Coverage
    • Stress test on RC
    • Compliance test on RC
    • Distribution test on RC

Test Automation

  • Objectives
    • Reduce effort with manual testing, by automating current tests;
    • Improve run-time testing.

Validation

  • Objective
    • Verify the correct functionality of new changes introduced in version 1.5 of the Yocto Project.
  • Entry criteria
    • The change is tracked and prioritized in Bugzilla;
    • Bugzilla entry has a target milestone within version 1.5;
    • The change is documented or pointed out when no documentation is necessary;
    • Bug status is set to RESOLVED.
  • Exit criteria
    • The change is well documented for writing test case, where applicable;
    • Planned test case has passed;
    • Bug status is set to VERIFIED.

Test Report

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_1.5_Overall_Test_Plan&oldid=10598"