Kernel Development QA

This article is the test plan for Kernel Development.

About Kernel Development

Extensible SDK makes it easy to add new applications and libraries to an image, edit the source for an existing component, test the changes on the target hardware, and also allow you to integrate into the rest of OpenEmbedded build system. In order to Setting up the extensible SDK please go to Setting Up to Use the Extensible SDK.

Objectives

Verify all Kernel Development components to be fully functional. Components to be verified:

• linux-yocto-custom
• local source
• local source with parallel meta
• local source with recipe-space meta
• External Source
• defconfig
• defconfig + fragments
• linux-yocto meta data + local fragments
• building external modules (hello-mod)

Team members

QA Team involved in Kernel Development testing

Francisco Pedraza 

Scope

• linux-yocto-custom
• local source.
• local source with parallel meta.
• local source with recipe-space meta.
• External Source
• defconfig
• defconfig + fragments
• linux-yocto meta data + local fragments.
• building external modules (hello-mod).

Test Strategy

There are several test approaches for Kernel Development, such as: Perform test cases agreed upon the development during periodic Manual (full pass) according to the Schedule. Write new test cases based on developer request or new features as required. Maintain current test cases and update them accordingly the new changes. Perform exploratory testing on existing functionalities.

Test automation

Not required until now.

Test Approach

Sanity testing

• Not covered at this moment
• TBD following DEV discussions

Performance and Stress

• Usability

Regression

• Regression testing will be covered on Automation execution.

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 and are tracked into Bugzilla, the official Yocto Project bug tracker. Learn more about our process for reporting bugs.

Requirements

This set of requirements is listed in a two column format, Bugzilla entries vs. requirement description in the form of a user story.

8137 As a developer I want to be able to install needed development libraries and headers from published sstate feeds. - Test Case 1471

additional detailed information about builds history. -

HW Requirements

• Any machine able to build Yocto Project.

Software Requirements

• poky.
• GNU/Linux environment

Environment Requirements

• • YP 2.1 Release:
  • Ubuntu-14.04
  • Ubuntu-14.10
  • Ubuntu-15.04
  • Fedora-21
  • CentOS-6.*
  • CentOS-7.*
  • Debian-7.*
  • Debian-8.*
  • openSUSE-project-13.2

Features

Features to be 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.

6.building external modules (hello-mod).

Schedule

Every cycle depending on Milestone and release candidate

Test execution Cycle

Build	Automated Test	Manual Test
Daily Master	Y	NO
Weekly Build	In progress	Y
Milestone Build	Y	Y

Dependencies

• YP Dependencies
  • poky
  • meta-kerneltest recipe

Risk Assumptions

• The complete features will not be tested now, the design of the test cases is under construction.

Tools

TBD