Yocto 1.3 Overall Test Plan
Yocto 1.3 Overall Test Plan reversion history
|0.3||Jiajun Xu||Initial Version|
|0.4||Jiajun Xu||Updated with comments from Yi Zhao, Hongna Xu and Yilong Sun|
Yocto 1.3 Overall Test Plan
This overall test plan defines test scope, test strategy, test configurations as well as test execution cycle for Yocto v1.3 program.
Components to Be Tested
- Core OS: The core OS feature included Yocto kernel, distro components(like connman & zypper), file system, device drivers (e.g. Intel Graphics Driver).
- Core build system: It includes basic core build test and other build feature test. Performance and different distribuitions support will be tested also.
- Hob2 & WebHob: It includes functional tests for both frontend and backend of Hob2 and WebHob.
- Yocto ADT: It includes cross-toolchain, Eclipse plugin tests.
- Power/Performance: QA will check the CPU power behavior by software level tool, such as powertop. Real Power consumption with idle is collected.
What will not Be Tested in Yocto v1.3
Following feature categories won't be tested by QA team in Yocto v1.3:
- Documentation: QA will not validate the correctness of each documentation.
- License file: license files and legal process is owned by Distro team.
Test Platform matrix
Following matrix is the target Test Plantforms for Yocto 1.3, with the target images will be validated in QA test.
|Category||Qemu||Atom||Core i7||Xeon||ARM HW||PPC HW||MIPS HW|
|Platform||FishRiver Island2||TunnelCreek||Blacksand||eMenlow||Chief River||Maho Bay||Sugarbay||HuronRiver||Romely||JasperForest||Beagleboard||mpc8315e-rdb||routerstationpro|
- Fullpass testing defined in execution plan will be performed against sato and sato-sdk image.
- For minimal image, only booting case is checked
Test Strategy and Approach
QA will cover following tests for each target in each round fullpass testing.
|Test Target||System & Core OS||ADT||Compliance||Stress||Power/Performance||Graphics||Mulitimedia|
|TunnelCreek noemgd||(basic functionality are tested)|
|FishRiver Island 2||yes||yes||yes|
- Compliance Test on Beagleboard and routerstation will only cover LTP and POSIX Test, since LSB test suite does not support ARM and MIPS.
- Jasperforest and Romely are picked up for stress test, because it is powerful with 12 CPUs and 2GB memory. Moreover, it is a server, which needs more stress tests. The other test boards, like blacksand and eMenlow do not have powerful CPUs, that's why we do not use them for stress test.
|Core build feature||Functionality||Performance||Distribution Support|
|WebHob & Hob2||yes||n/a||n/a|
|Other build features||yes||n/a||n/a|
- For other core build features not listed, QA will cover functionality test if there is no specific requirement for performance and distribution.
The Yocto 1.3 will be tested from the following different test execution levels.
Sanity Test is a very brief and quick test. It is integrated with each build process (including incremental build) in autobuilder system. It checks image basic functionality, such as booting, network, zypper 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.
Test Frequency: Sanity test will be run on autobuilder system against daily build image.
Test Scope: Sanity test only check very basic functionality in QEMU and its execution time is less than 10 minutes.
Regression test is a set of tests to verify the new feature development does not introduce new issues to previous workable functionality. It covers the most important features check for both BSP/QEMU and yocto build features. The testcase list is updated after one milestone is finished and won't be updated until the next milestone is finished.
Test Frequency: Regression test will be run on PRC autobuilder system against daily build image.
Test Scope: Regression Test covers more cases than Sanity Test. It includes functionality check in QEMU and the basic check for yocto build features.
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 Regression Test. Weekly test will also manually check key components behavior, such like X window, connman, multimedia.
Test Frequency: Weekly Test is against weekly image and occurred each Thursday if image is ready on autobuilder system. It will cost 3 days for one round weekly test.
Test Scope: Weekly Test covers more cases than Regression Test. It includes more manual cases for QEMU and yocto build features.
In milestone test, test team will perform a full validation testing for candidate build, following test will be involved. It includes more tests than Sanity and Weekly Test.
- Functional Test – which will test the items in Feature List(defined in https://wiki.yoctoproject.org/wiki/Yocto_1.3_Schedule), cover Core OS & System usage, WebHob, Hob2, and other build features, etc.
- Stress Test – system should be alive and functional in 24 hours workload test.
- Power and Performance Test – which follow the power and performance test plan
- Compliance Test - system level test suites will be chosen, LTP, POSIX and LSB.
Test Frequency: Fullpass test will be performed against each RC build for milestone. It will cost a whole week for one round fullpass test.
Test Scope: Fullpass Test covers more cases than Weekly Test. It includes stress test, power test, as well as compliance test.
Functional Test is a set of tests to verify if new features listed in Yocto 1.3 could work as expected. QA needs to update the whiteboard for each feature in bugzilla with following status:
- Test Plan Ready: It means QA has discussed with developers and understood how to test a new feature. Testcase design has been reviewed by developer. QA should set the status during a feature is in Design or Design Review stage.
- Test Case Completed: It means QA has finished testcases implementation for a new feature. QA should set the status afer a feature is Development Finished.
- QA Testing Completed: It means QA finishes validation of a new feature and send the result on bugzilla or send to developer.
- No QA needed: It means there is no need to design any testcases for a new feature or QA has no resource to cover it.
- Covered by current QA Test Plan: It means current QA test plan already covers the feature. No new cases needed.
Test Frequency: New Feature test is a continuous QA work within feature development phase. After one new feature is finished, testcases for it will be added into weekly or fullpass test.
Test Execution Cycle
|Build||Sanity Test||Regression Test||Weekly Test||Fullpass Test|
|Daily Full Build||yes||yes|
Test report should be posted on webpage and Yocto mailing list.
|Test Report||AutoBuilder Web||Yocto Mailing List|
|Daily Full Build||yes|
Test report format : Test Report Format
To reduce testing time, test automation will be adopted in the testing. Part of following tests will be implemented as automation:
- BSP/QEMU functionality tests
- Build feature tests
Note: Currently only sanity tests(10 cases) are fully automated.
If QA has resource, test infrastructure will be investigated in Yocto v1.3. Automation test cases development should be test infrastructure independent.
This is a overall test design for test components which will be covered QA testing. Detailed test cases design will be covered in Test Execution Plan.
System & Core OS(Covered in Weekly/Fullpass Test)
- 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 for software update 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:
- Rootless X
- ... etc
(Basic functionality for tested features will be exercised as well as new functionality added in each release.)
Core Build System(Covered in Weekly/Fullpass Test)
- Functionality Test: Test Core build feature on standard host configuration. For example:
- Build Appliance
- PR service
- Package History
- ... etc
- Distribution support Test: Test Core build on latest CentOS, Ubuntu, Fedora and Opensuse Hosts
- WebHob & Hob2 Test: Main UI and component functionality are validated
- Performance Test: Check Core build performance on standard host(Defined in perfromance test webpage)
ADT Test(Covered in Weekly Test)
- Cross-toolchain install&compiling Test
- ADT installer
- toolchain tarball
- yocto build tree
- Eclipse plugin
- C/C++ project create/cross-compile/remote-debug/deploy
- User-Space Tools
- Bitbake Project Create
- Distribution Support
- 32/64 bit, QEMU/BSP support
- Ubuntu, Fedora, Opensuse
Stress Test(Covered in Fullpass Test)
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: 24 hours workload (Helltest + Crashme) test should pass.
Power/Performance Test(Covered in Fullpass Test)
Power/Performance Test is to collect the power/performance data and status of Yocto image on defined BSP.
- Test Method: Power test will check if Yocto is power saving friendly, that CPU should support and enter different power saving stage.
Compliance Test(Covered in Fullpass Test)
Compliance Test is targeted to validate system level health with different system test suite.
- LTP test suite
- POSIX test
- LSB test