Toaster testing plan

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_Contracts | REST API] verification – create Django tests in order to detect API calls returning no data;
• 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);