Toaster testing plan: Difference between revisions
From Yocto Project
Jump to navigationJump to search
No edit summary |
|||
| Line 9: | Line 9: | ||
* Backend interaction with bitbake for build purposes | * Backend interaction with bitbake for build purposes | ||
* Backend interaction with database for storing and accessing build information | * Backend interaction with database for storing and accessing build information | ||
The testing objective involves only positive testing for existing features on Toaster. | |||
Perform exploratory testing focusing on newer features | |||
*this can sometimes generate new test cases. | |||
Verifying the bugs and features. | |||
= Team members = | = Team members = | ||
Revision as of 13:07, 4 December 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
The testing objective involves only positive testing for existing features on Toaster.
Perform exploratory testing focusing on newer features
- this can sometimes generate new test cases.
Verifying the bugs and features.
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
