Yocto 2.1 Overall Test Plan: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 544: Line 544:
# Put the tests from Testopia - Runtime test run on passed
# Put the tests from Testopia - Runtime test run on passed


;[TBD] - update this doc with contrib for compliance_test.py and ptest-runner.sh
The scripts can be found here: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=cagurida/compliance


== pTest ==
== pTest ==

Revision as of 13:57, 15 January 2016

Reversion history

Version Modifier Comments
1.0 Alexandru Georgescu first draft


Introduction

This article is the overall test plan for version 2.1 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 and Tasks

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.


Objectives

The Overall testing plan during Yocto Project 2.1 cycle aims to validate the overall enhancements that are currently in development for Yocto Project 2.1 as well as detecting regressions that might appear along.

  • Bug and feature verification
  • Running regression tests
  • Perform exploratory testing on required areas (e.g. Toaster)

[TBD]


Tasks

Here is a list with all tasks identified by this testing plan.

  • Testing
  • Bug and Feature reporting
  • Bug and Feature verification
  • Test automation
  • Exploratory testing
  • Creating testing plans for specific areas
  • Review testing approaches with development peers
  • Assign owners on major features

Testing Strategy

Test Areas

By definition, Yocto Project is an open source collaboration project that provides templates, tools and methods to help you create custom Linux-based systems for embedded products regardless of the hardware architecture. Therefore, 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.

Toaster

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 against Toaster. The test process focuses mostly on validating the data collected from the build process and verifying the correct functionality of the Toaster GUI such as:

  • UI interface
  • Backend interaction with bitbake for build purposes
  • Backend interaction with database for storing and accessing build informations
  • The testing objective involves only positive testing for existing features on Toaster.
  • Perform exploratory testing focusing on newer features; this can sometimes generate new test cases.

Metadata

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

Distro Testing

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 are Fedora, Ubuntu, CentOS, OpenSuse with their latest update. If for a distribution, a beta version is available during the release, the n+1 (beta version) will be validated as well.
Refer to Distribution Support wiki for more details.

[TBD] - distribution support wiki needs to be updated

Runtime testing

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.

CPU Class HW Platform BSP Name linux-yocto Image-type Sanity Testing Weekly Testing Full pass Compliance pTest
Big Core MinnowMax 32bit genericx86 4.x core-image-sato-sdk Y Y Y NO Y
4.x-ltsi core-image-lsb-sdk NO Y NO NO NO
MinnowMax 64bit genericx86-64 4.x core-image-sato-sdk Y Y NO NO NO
4.x-ltsi core-image-lsb-sdk NO NO NO NO NO
NUC genericx86-64 4.x core-image-sato-sdk Y Y Y NO Y
4.x-ltsi core-image-lsb-sdk NO Y NO Y NO
genericx86-64-wic 4.x core-image-sato Y Y NO NO NO
4.x-ltsi core-image-lsb-sdk NO NO NO NO NO
arm Beaglebone Black beaglebone 4.x core-image-sato Y Y Y NO NO
4.x-ltsi core-image-lsb-sdk NO NO No Y NO
ppc MPC8315e-rdb mpc8315e-rdb 4.x core-image-sato Y Y Y NO NO
4.x-ltsi core-image-lsb-sdk NO NO No Y NO
ppc P1022ds p1022ds 4.x core-image-sato Y Y Y NO NO
4.x-ltsi core-image-lsb-sdk NO NO No NO NO
mips64 Edgerouter edgerouter 4.x core-image-sato Y Y Y NO NO
4.x-ltsi core-image-lsb-sdk NO NO No Y NO
VM QEMU qemux86 4.x core-image-sato-sdk Y Y Y NO NO
4.x-ltsi core-image-lsb-sdk NO NO NO NO NO
qemux86-64 4.x core-image-sato-sdk Y Y Y NO NO
4.x-ltsi core-image-lsb-sdk NO NO NO NO NO
qemuarm 4.x core-image-sato-sdk Y Y Y NO NO
4.x-ltsi core-image-lsb-sdk NO NO NO NO NO
qemuarm64 4.x core-image-sato-sdk Y Y Y NO NO
4.x-ltsi core-image-lsb-sdk NO NO NO NO NO
qemuppc 4.x core-image-sato-sdk Y Y Y NO NO
4.x-ltsi core-image-lsb-sdk NO NO NO NO NO
qemumips 4.x core-image-sato-sdk Y Y Y NO NO
4.x-ltsi core-image-lsb-sdk NO NO NO NO NO
qemumips-64 4.x core-image-sato-sdk Y Y Y NO NO
4.x-ltsi core-image-lsb-sdk NO NO NO NO NO


Sanity Testing

[TBD]

Weekly Testing

[TBD] - add Weekly templates Automated BSP tests, are targeted to run on a weekly basis against the weekly build. Enabling and running the tests is described on the Image tests wiki page. The tests are available for QEMU BSPs and as well BSPs installed on real HW.


Full Pass

[TBD] - add FP templates The full pass testing aims to run the BSP test cases that are not automated. They extend what is covered by #Weekly Testing by containing more complex scenarios like changing runlevels, or audio tests.


Stress Testing

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

System Performance

  • Objective
    • Track the run-time performance of targeted systems;
    • Track the run-time performance of targeted systems with gcc security flags;
  • Indicators
    • Boot time for systemd and sysvinit;
    • Image size from Buildhistory to track regression;
    • Piglit test suite results;
    • Other benchmarks that can be integrated, such as the ones listed in the openbenchmarking site.

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

Depending on the new SDK features (e.g. MacOS and Windows support), additional tests will be run in order to validate the new features.

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.7 release date is: OCT, 2014)
Coverage
Following a table with targeted distribution and versions:
TBD
Add Distro testing information and get info from DEV on how often Distro need to be updated

Testing tools

Autobuilder

[TBD] add info

Autobuilder

oe-selftest

Oe-selftest is a test framework used for testing the OpenEmbedded build system. Following are some key points in describing oe-selftest:

  • based on Python unittest
  • designed to simulate normal usage patterns
  • does not cover image run-time testing
  • implements a new layer that contains generic/specific metadata used only by tests

Details regarding oe-selftest implementation and usage are available on Oe-selftest wiki.

Image tests

Compliance Testing

Compliance test suites / frameworks used on genericx86-64:

  • LSB tests
  • POSIX tests
  • LTP tests


  1. Download lsb image from autobuilder( same image as in LSB weekly testing for genericx86-64-lsb bsp)
    • we test compliance on NUC with genericx86-64-lsb, core-image-lsb-sdk
  2. Install the image on DUT
  3. Configure the network so it be able to work externally:
    • edit /etc/resolv.conf and add the gateway ip_address
    • add the ip and netmask using "ifconfig" command
    • add the route using "route add default gw <ip_address>"
    • export the proxy using "export http_proxy=<add your proxy link>" command
    there is a bug and if you make these steps in another order than above, it may be possible not work
  4. Copy "compliance_test.py" script on DUT
  5. Make sure that your network connection is working
  6. Run the script like this:
    • make the script executable: "chmod a+x compliance_local.py"
    • run in command line the following command "./compliance_test.py <milestone> <date>"
    • wait until "Configuration done. LSB script must be started from machine." in command line( about 8-12 hours)
  7. Run "LSB_test.sh" via ssh or manually and wait for it to finish( about a day)
  8. Get the logs from DUT:
    • result-<milestone>-data.fulllog
    • result-<milestone>-data.log
    • result-<milestone>-data.fail
    • posix.log (can be found in: /opt/ltp/testcases/open_posix_testsuite)
      • the three others are found in /opt/ltp directory, in output, temp, result folders . The logs need to be sent to yi.zhao@windriver.com specifying the version and the type of image
    • in /var/opt/lsb/test/manager/results/x86.../x86....tar.gz (you can find it with auto-complete(tab) easily)
  9. Put the tests from Testopia - Runtime test run on passed

The scripts can be found here: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=cagurida/compliance

pTest

Ptest (package test) is a concept for building, installing and running the test suites that are included in many packages, and producing a consistent output format. More details on enabling and installing pTest are available on pTest wiki.

  1. Download pTest image from autobuilder( you can find core-image-sato-sdk image in pTest directory)
  2. Install the image on DUT (using legacy boot)
  3. Boot the image and copy "ptest-runner.sh" script on DUT
  4. In command line run "ptest-runner.sh > ptest.log" and wait for it to finish ( about 5 hours)

Build Performance test

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

The tool used: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/contrib/build-perf-test.sh
For more details, refer to Performance Test wiki.
Currently, build performance results can be viewed here as chart view (starting YP 1.6) here

Automatic testing of incoming patches

Test Cycle

  • 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
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
#Toaster 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
Distro Testing yes
Target machine
qemuarm yes yes yes
qemumips yes yes yes
qemuppc yes yes yes
qemux86 yes yes yes
qemux86-64 yes yes yes
genericx86-64 yes yes
genericx86-64 yes yes
beaglebone black yes yes yes
mpc8315e-rdb yes yes
edgerouter 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.
    • 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.

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.
    • Improve build-time testing.


Contrib repositories

[AR ALL] - please add info here

Eclipse testing framework - http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=vhangan/eclipse-dogtail&id=1438e4967579508c2f6101ab778fe28af344e63b

Validation

  • Objective
    • 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

Test Report

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_2.1_Overall_Test_Plan&oldid=17054"