Yocto 1.5 Overall Test Plan: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
No edit summary
Line 6: Line 6:
| 1.0 || Alexandru Georgescu || Initial Version  
| 1.0 || Alexandru Georgescu || Initial Version  
|}
|}
== Yocto 1.5 Test Execution Plan ==
This test plan defines test targets/components, scope, strategy, configurations as well as test execution cycles for 1.5 version of Yocto.
=== Targets / Components to Be Tested ===
* Core OS: The core OS feature included Yocto kernel, distribution components(like connman, smart updater & zypper), file system. [TODO]
* Core build system: includes build system tests also using additional features and tweaks for it.
* Hob2: It includes functional tests for both frontend and backend of Hob2.
* Yocto ADT: It includes cross-toolchain, Eclipse plugin tests.
* 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. [TODO]
* 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).[TODO]
* Compliance testing: LSB, LTP and POSIX tests are ran on the the selected targets. [TODO]
* Stress testing: Helltest + Crashme test suites are ran.[TODO]
=== What will not Be Tested in Yocto v1.5 ===                                                                                                                                                                           
Following feature categories won't be tested by QA team in Yocto v1.5:
* Documentation: QA will not validate the correctness of each documentation.
* License file: license files and legal process are owned by Distro team.
[TODO]
=== Test Environment ===
==== Test Platform matrix ====
[TODO] - add the test platform matrix with all the core bsps that tests will be performed on
Notes:
* Fullpass testing defined in execution plan will be performed against sato-sdk image.
* The atom images are both emgd and no-emgd images

Revision as of 10:45, 17 May 2013

Yocto 1.5 Overall Test Plan reversion history

Version Modifier Comments
1.0 Alexandru Georgescu Initial Version


Yocto 1.5 Test Execution Plan

This test plan defines test targets/components, scope, strategy, configurations as well as test execution cycles for 1.5 version of Yocto.

Targets / Components to Be Tested

  • Core OS: The core OS feature included Yocto kernel, distribution components(like connman, smart updater & zypper), file system. [TODO]
  • Core build system: includes build system tests also using additional features and tweaks for it.
  • Hob2: It includes functional tests for both frontend and backend of Hob2.
  • Yocto ADT: It includes cross-toolchain, Eclipse plugin tests.
  • 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. [TODO]
  • 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).[TODO]
  • Compliance testing: LSB, LTP and POSIX tests are ran on the the selected targets. [TODO]
  • Stress testing: Helltest + Crashme test suites are ran.[TODO]

What will not Be Tested in Yocto v1.5

Following feature categories won't be tested by QA team in Yocto v1.5:

  • Documentation: QA will not validate the correctness of each documentation.
  • License file: license files and legal process are owned by Distro team.

[TODO]

Test Environment

Test Platform matrix

[TODO] - add the test platform matrix with all the core bsps that tests will be performed on

Notes:

  • Fullpass testing defined in execution plan will be performed against sato-sdk image.
  • The atom images are both emgd and no-emgd images