Toaster testing plan: Difference between revisions
From Yocto Project
Jump to navigationJump to search
| Line 16: | Line 16: | ||
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning no data; | * [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning no data; | ||
* Calculation of the data collection rate; | * Calculation of the data collection rate; | ||
* Verify | * Verify that all links in the simple UI are available; | ||
* Verify the quality of the data collected through the simple UI; | * Verify the quality of the data collected through the simple UI; | ||
Revision as of 14:53, 21 October 2013
Introduction
This article is the test plan for Toaster.
Objectives
The test process focuses on:
- validating the data collected from the build process
- verifying the correct functioning of the Toaster GUI.
Test Areas
Toaster consists of two big components, as follows:
1. Backend
Functionality tests
- REST API verification – create Django tests to detect API calls returning no data;
- Calculation of the data collection rate;
- Verify that all links in the simple UI are available;
- Verify the quality of the data collected through the simple UI;
Usability tests
- Verify the easy usage of the Toaster (easy to install and stop/start the toaster server)
2. Frontend
Functionality tests
- Manual testing in the first stage;
- Automate testing using Selenium, in the second stage;
Compatibility tests
- Verify the behavior of the GUI on different browsers and operating systems;
Usability tests
- Verify if the GUI design is as described here: https://wiki.yoctoproject.org/wiki/WebHob#User_interface;
- Friendly graphical user interface;
Performance tests
- Stress testing (e.g. display appropriate error messages when the system is under stress);
