Toaster testing plan

From Yocto Project
(Difference between revisions)
Jump to: navigation, search
(Usability tests)
Line 15: Line 15:
 
==== Functionality tests ====
 
==== Functionality tests ====
 
*  [[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 - the ratio of the number of the variables having null values ​​and the total number of variables collected;
 
*  Verify that all links in the simple UI are available;
 
*  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;
Line 32: Line 32:
  
 
==== 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: http://yoctoproject.org/webhob;
 
*  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 08:05, 21 October 2013

Contents

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 - the ratio of the number of the variables having null values ​​and the total number of variables collected;
  • Verify that all links in the simple UI are available;
  • Verify the quality of the data collected through the simple UI;

Usability tests

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

Performance tests

  • Stress testing (e.g. display appropriate error messages when the system is under stress);
Personal tools