Toaster testing plan
From Yocto Project
Jump to navigationJump to search
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
Testing scope has been agreed upon as local installation only, using sqlite database on Fedora and Ubuntu operating systems on Firefox browser.
New features are to be tested as they are finished with test cases written for them once features are stabilized.
UI features being tested:
- Create new project
- Modify project settings and variables
- Add/Remove layers to project
- Building images
- Build details
- All builds report table
Backend features:
- Toaster installation and first time configuration
- Data presence
- Data consistency
- Build data
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
