Kernel Development QA
This article is the test plan for kernel development features in Yocto Project.
About Kernel Development
Describes common tasks you can perform on Yocto Project using kernel tools, and shows you how to use the metadata required to work with the kernel. For more information you can review the Kernel Development manual.
Objectives
Verify all kernel development components are fully functional.
Team members
QA team members involved in Kernel Development testing:
Jair Gonzalez
Scope
Types of Tests
- Manual tests on different platforms
- No automated tests at the moment
Features Tested
- 1. linux-yocto-custom
- 1.1 local source
- 1.2 local source with parallel meta
- 1.3 local source with recipe-space meta
- 2. External Source
- 3. defconfig
- 4. defconfig + fragments
- 5. linux-yocto meta data + local fragments (WIP)
- 6. building external modules (hello-mod)
The complete set of test cases are documented on the Kernel Development Test Cases wiki. They are also listed on the master Kernel test plan in Testopia, that can be reached following this link.
Test Strategy
There are several test approaches for kernel development, such as:
- Perform test cases agreed upon development during periodic full pass test cycles, according to the schedule.
- Write new test cases based on developer requests or new features added, as required.
- Maintain current test cases and update them according to changes.
- Perform exploratory testing on existing functionalities.
Test automation
Tests will be gradually automated, after determining the feasibility to do so following discussions with the development team.
Sanity testing
- Not covered at this moment
- TBD following discussions with the development team
Test Process
- 1. Follow the steps as indicated on the Kernel Development Test Cases wiki.
- 2. Verify that all test cases pass. If not, raise bugs properly.
- 3. Update results to corresponding Testopia test run.
Submitting Bugs
Being part of the Yocto Project, Kernel Development follows the same Yocto Project guidelines and principles. The guidelines can be found at https://wiki.yoctoproject.org/wiki/Community_Guidelines. Kernel Development bugs are no different than other Yocto Project bugs and are tracked into Bugzilla, the official Yocto Project bug tracker. Learn more about our process for reporting bugs.
Requirements
Use cases are documented in the corresponding section for each test case on Kernel Development Test Cases wiki.
HW Requirements
- Any machine able to build Yocto Project.
Software Requirements
- Poky
- GNU/Linux environment
Environment Requirements
- YP 2.3 Release:
- Ubuntu-14.04
- Ubuntu-14.10
- Ubuntu-15.04
- Fedora-21
- CentOS-6.*
- CentOS-7.*
- Debian-7.*
- Debian-8.*
- openSUSE-project-13.2
Schedule
Every cycle depending on Milestone and release candidate
Test execution Cycle
| Build | Automated Test | Manual Test |
|---|---|---|
| Daily Master | NO | NO |
| Weekly Build | TBD | TBD |
| Milestone Build | TBD | Y |
Dependencies
- YP Dependencies
- poky
- meta-kerneltest layer
Risk Assumptions
- For each change in kernel version and kernel cache, the team needs to change many configuration files in order to achieve a correct execution.
- Just like any software, the kernel is also susceptible to bugs.
Tools
- bitbake
- yocto-layer
- bitbake-layers
- any available text editor
Release Criteria/ Exit Criteria
- All test cases pass.
- No blocking issues are found.
References
- http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html
- http://www.yoctoproject.org/docs/latest/kernel-dev/kernel-dev.html
Compendium of Yocto Project manuals, including the two above:
