Toaster testing plan: Difference between revisions
From Yocto Project
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
= Assumptions/Risks = | = Assumptions/Risks = | ||
= Test Approach = | = Test Approach = | ||
Overall approach to testing. Specify major activities, techniques and tools used to test groups of features | |||
== Regression Testing == | |||
== Performance and stress testing == | |||
== Test Automation == | == Test Automation == | ||
= Test environment = | = Test environment = | ||
| Line 19: | Line 24: | ||
== Test schedule == | == Test schedule == | ||
== Deliverables == | == Deliverables == | ||
* Features to be tested | |||
= Resources roles & responsibilities= | |||
= Release Criteria/ Exit Criteria = | |||
= Dependencies = | |||
* Personal Dependencies | |||
* Software Dependencies | |||
* Hardware Dependencies | |||
= Risks = | |||
== Schedule== | |||
== Technical == | |||
== Requirements == | |||
= Tools = | |||
= Documentation = | |||
Revision as of 12:07, 29 October 2015
This article is the test plan for Toaster.
Objectives
Verify all Toaster components to be fully functional.
Components to be verified:
- UI interface
- Backend interaction with bitbake for build purposes
- Backend interaction with database for storing and accessing build information
Team members
Scope
Assumptions/Risks
Test Approach
Overall approach to testing. Specify major activities, techniques and tools used to test groups of features
Regression Testing
Performance and stress testing
Test Automation
Test environment
Deliverables
Test schedule
Deliverables
- Features to be tested
Resources roles & responsibilities
Release Criteria/ Exit Criteria
Dependencies
- Personal Dependencies
- Software Dependencies
- Hardware Dependencies
