Extensible SDK Test Plan (eSDK)

From Yocto Project
Jump to navigationJump to search

This article is the test plan for eSDK.

About eSDK

Extensible SDK makes it easy to add new applications and libraries to an image, modify the source for an existing component, test changes on the target hardware, and ease integration into the rest of the Open Embedded Build System

Objectives

Team members

QA Team involved in eSDK testing

Francisco Pedraza 

Scope

Test Strategy

Test automation

Test Approach

Sanity testing

Performance and Stress

Load testing

System Integration Testing

Regression

Maintaining the test cases

Submitting Bugs

Being part of the Yocto Project, eSDK follows the same Yocto Project guidelines and principles. The guidelines can be found at https://wiki.yoctoproject.org/wiki/Community_Guidelines. eSDK bugs are no different and are tracked into Bugzilla, the official Yocto Project bug tracker. Learn more about our process for reporting bugs.

Requirements

HW Requirements

Software Requirements

Environment Requirements

Features

Features to be tested

1. Ability to install needed development libraries and headers from published sstate feeds.

2 .Extensible SDK: distributable sstate cache for individual componets

3. Extensible SDK: ability to generate images out of binary feeds

4. Publish eSDK with modifications/addons

5. eSDK image creation benchmark

6. eSDK software development benchmark

7. Node.js modules' install in bitbake output.

8. Devtool: create proper recipes for Node.js modules.

9. Recipetool: extend cmake recipe creation.

10. Devtools/recipetool: support adding off-tree kernel module.

11. Devtool/recipetool: easy way to create kernel recipe with custom .config.

Schedule

Test execution Cycle

Dependencies

Risk Assumptions

Tools

Release Criteria/ Exit Criteria