Extensible SDK Test Plan (eSDK): Difference between revisions
From Yocto Project
Jump to navigationJump to search
| Line 49: | Line 49: | ||
==Features to be tested== | ==Features to be tested== | ||
<p>1. Ability to install needed development libraries and headers from published sstate feeds.</p> | <p>1. Ability to install needed development libraries and headers from published sstate feeds.</p> | ||
<p>2 .Extensible SDK: distributable sstate cache for individual componets</p> | |||
<p>3. Extensible SDK: ability to generate images out of binary feeds</p> | |||
<p>4. Publish eSDK with modifications/addons</p> | |||
<p>5. eSDK image creation benchmark</p> | |||
= Schedule = | = Schedule = | ||
Revision as of 20:51, 20 May 2016
This article is the test plan for eSDK.
About eSDK
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
