Test Levels

The Yocto 0.0 will be tested from the following different test execution levels.

Sanity Test

Sanity Test is a very brief and quick test. It is integrated with each build process (including incremental build) in auto build system. It checks image basic functionality, such as booting, network, sdk compilation etc. Its results will be published in build web page and referred by the other testing. It is fully automation test and its execution time should be less than 10 minutes.

BAT Test

Basic Acceptance Test (BAT) is a fully automation test. It will be executed after full build check in auto build system. It checks more fields than Sanity Test, e.g. some system level test, such as LTP. Its execution time should be controlled within 2 hours.

BAT test depends on Sanity Test result. If Sanity Test is failed, BAT test will not be executed.

Weekly Test

Weekly test is a test cycle against the weekly image released through distribution team. It will do new feature exploring, bug verification and regression testing. It includes more testing in component and system usage rather than BAT Test. Weekly test will also manually check key components behavior, such like X window, web browser.

Fullpass Test

In milestone test, test team will perform a full validation testing for candidate build, following test will be involved:

Weekly Test - In fullpass test week, there will not be alone weekly test. Weekly test contents should be firstly executed for milestone build.

Functional Test – which will follow the Feature List to test.

Stress Test – system should be alive and functional in 72 hours workload test.

Power and Performance Test – which follow the power and performance test plan

Regression Test

Regression test is a set of tests to verify that change from the last build (code enhancements, bug fixes) doesn’t introduce new issues to the previous working code as well as new features work as expected. This cycle includes the tests for previous major bug fixes and areas of the code that might be affected by new implementation.

The regression test will be taken in following test cycle:

Weekly testing

Fullpass testing

Test Execution Cycle

Build

Sanity Test

BAT Test

Weekly Test

Fullpass Test

Incremental Build

yes

Daily Full Build

yes

yes

Weekly Build

yes

yes

yes

Milestone Build

yes

yes

yes

yes

Test Report

Test report should be posted and archived.

Test Report

AutoBuilder Web

Yocto Mailing List

Wiki Archieve

Incremental Build

yes

Daily Full Build

yes

Weekly Build

yes

Milestone Build

yes

yes

Test report format : TBD

Test Automation

To reduce testing time, test automation will be adopted in the testing. Following test will be implemented as automation:

Sanity Test

BAT Test

System Test (LTP, POSIX, LSB etc.)

Stress Test

Performance Test

Test Infrastructure

Test infrastructure will be considered in Yocto v0.9 . Automation test cases development should be test infrastructure independent.

Test Design

Core OS

Boot Test: Check if Yocto image is bootable with the bootloader.

Compliance Test

LTP test suite

POSIX test

LSB test

Component Test (aka. Feature Test): Based on minimal and sato image features to test, such as connman, web browser, X etc.

Developer unit test suite

Wind River Test Suite: any Wind River test suite for embedded Linux can be used in Yocto

Installation/SW Update

Test Method:

Validate the Yocto image installation on hardware platform and software update functions from the end users' perspective.

SDK Test

standalone SDK compilation test. The target application could be compiled success and executable in target platform.

SDK plugin functional test. It is based on SDK HLD definition.

Stress

Stress testing refers to tests that determine the robustness of software by testing beyond the limits of normal operation. Stress tests commonly put a greater emphasis on robustness, availability, and error handling under a heavy load, than on what would be considered as correct behavior under normal circumstances.

Test Method:

72 hours workload test should pass.

Power

Test Method:

Power test will check if Yocto is power saving friendly, that CPU should support and enter different power saving stage.

Performance

Test Method:

Industry standard benchmark will be executed. The performance results should be collected and published for analysis and tuning.