Yocto 1.8 Overall Test Plan
|1.0||Alexandru Georgescu||first draft|
This article is the overall test plan for version 1.7 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.
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.
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:
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.
Functional testing of BitBake, as a build engine with all its features and components against various configuration and scenarios.
Functional and usability testing of HOB as a graphical user interface for BitBake.
Toaster is a Web-based interface to the Bitbake build system and the Poky distribution inside the Yocto Project. This project was formely known as Web Hob / Webhob / webhob, and you may still find references to the old name in the documentation. The Toaster testing plan wiki covers all the validation performed agasint Toaster. The test process focuses mostly on validating the data collected from the build process and verifying the correct functionality of the Toaster GUI.
The performance of the build system is tracked, with regards to time spent on passing through a build process, in multiple, commonly used, configurations.
- Results page
- Performance Test
Additionally, build performance will be tracked with/without security flags enabled. The first step is to have several build combinations of core-image-minimal, core-image-sato and core-image-sato-sdk and see the build time differences between the builds.
Distro Testing is intended to catch bugs that are distribution specific using the yocto-autobuilder. The tests are all run on identical hardware and with all OS-es updated. The distributions used will be Fedora, Ubuntu, CentOS, OpenSuse with their latest update. The buildsets that are running on Distro testing are:
- nightly x86-64
- nightly x86-64-lsb
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|
Covering all core, QEMU, machine definitions:
Covering BSPs included in the Yocto Project:
Compliance test suites / frameworks used on genericx86-64:
- LSB tests
- POSIX tests
- LTP tests
Stress tests are run on Beagleboard and genericx86-64 BSPs. Details as follow:
- Beaglebone core-image-sato-sdk image is tested using LTP and Crashme stress tests
- genericx86-64 core-image-lsb-sdk image is tested using Helltest and Crashme stress tests
- Track the run-time performance of targeted systems;
- Track the run-time performance of targeted systems with gcc security flags;
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
- user space tools
- Bitbake project
Depending on the new SDK features (e.g. MacOS and Windows support), additional tests will be run in order to validate the new features.
The basic functionality of the Build appliance will be tested. The tests consists on building successfully a build-appliance-image, launch HOB.
- The OS distribution version is still maintained at the time of the Yocto Project release (1.7 release date is: OCT, 2014)
- Following a table with targeted distribution and versions:
|14.04 LTS||April 17, 2014||April 2019|
|20||December 17, 2013|
|21||December 14, 2014|
|5||~||March 31, 2017|
|6||~||November 30, 2020|
|6||February 6th, 2011|
|7||May 4th, 2013||current|
|12.3||May 28, 2013||~|
|13.1||Nov 16, 2013||~|
- Execution according to Yocto 1.7 Schedule. The first section of the table, "Build Type", details what type of tests are performed on Weekly, Release Candidate or Release test.
- List of all Test Cases, included in a cycle or not.
|Test execution cycle|
|#Sanity Test||#Weekly Test||#Full Pass Test||#Release Test|
|#Application Development Toolkit||yes||yes|
|#Eclipse IDE Plugin||yes||yes||yes|
Brief and quick automated tests, with execution time of maximum 10 minutes.
- Each build process triggered on the AutoBuilder.
- 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.
- The tests run on AB are the Image tests. Their configurations are stored in the AB config files "yocto-autobuilder/buildset-config" depending on the target image types.
- Images built weekly and released through the distribution team.
- Passed #Sanity Test
- Functionality test on most areas with minimum sets of tests;
- Regression test with high probability to find bugs.
Full Pass Test
- Images built as candidates for milestone or final release;
- Passed #Weekly Test
- Ensure functionality of all Yocto Project components.
- Release candidates that pass #Full pass test
- All scheduled features are covered, or rescheduled;
- All relevant bugs are fixed and verified.
- Stress test on RC
- Compliance test on RC
- Distribution test on RC
- Reduce effort with manual testing, by automating current tests;
- Improve run-time testing.
- Improve build-time testing.
- Verify the correct functionality of new changes introduced in version 1.7 of the Yocto Project.
- Entry criteria
- The change is tracked by filling in the "QA Owner" field for the Medium+/High enhancements
- The change is prioritized in Bugzilla
- Bugzilla entry has a target milestone within version 1.7
- The change is documented or pointed out when no documentation is necessary (the doc flag is set accordingly)
- 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
New features validation and QA integration
- Some of the areas that need to be tested
- uClibc integration
- performance using gcc security flags
- Shuku proposal