Toaster testing plan: Difference between revisions
From Yocto Project
Jump to navigationJump to search
| Line 9: | Line 9: | ||
= Test Areas = | = Test Areas = | ||
Toaster consists of two big components, as follows: | |||
=== Backend === | === 1. Backend === | ||
==== Functionality tests ==== | ==== Functionality tests ==== | ||
| Line 22: | Line 22: | ||
* Verify the easy usage of the Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and stop/start the toaster server]) | * Verify the easy usage of the Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and stop/start the toaster server]) | ||
=== Frontend === | === 2. Frontend === | ||
=== Functionality tests === | ==== Functionality tests ==== | ||
* Manual testing in the first stage; | * Manual testing in the first stage; | ||
* Automate testing using [http://www.seleniumhq.org/ Selenium], in the second stage; | * Automate testing using [http://www.seleniumhq.org/ Selenium], in the second stage; | ||
=== Compatibility tests === | ==== Compatibility tests ==== | ||
* Verify the behavior of the GUI on different browsers and operating systems; | * Verify the behavior of the GUI on different browsers and operating systems; | ||
=== Usability tests === | ==== Usability tests ==== | ||
* Verify if the GUI design is as described here: https://wiki.yoctoproject.org/wiki/WebHob#User_interface; | * Verify if the GUI design is as described here: https://wiki.yoctoproject.org/wiki/WebHob#User_interface; | ||
* Friendly graphical user interface; | * Friendly graphical user interface; | ||
=== Performance tests === | ==== Performance tests ==== | ||
* Stress testing (e.g. display appropriate error messages when the system is under stress); | * Stress testing (e.g. display appropriate error messages when the system is under stress); | ||
Revision as of 14:50, 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 APIs verification – create django tests in order to find out what fields are empty from the response returned by the API called;
- Calculation of the data collection rate;
- Verify if all the links from 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);
