Toaster testing plan: Difference between revisions
From Yocto Project
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
= Team members = | = Team members = | ||
= Scope = | |||
= Assumptions/Risks = | |||
= Test Approach = | |||
== Test Automation == | |||
= Test environment = | |||
= Deliverables= | |||
== Test schedule == | |||
== Deliverables == | |||
| Line 17: | Line 35: | ||
<!-- | <!-- | ||
THIS IS THE OLD TESTING PLAN | |||
= Test Areas = | = Test Areas = | ||
Revision as of 09:12, 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
