Toaster testing plan

From Yocto Project
(Difference between revisions)
Jump to: navigation, search
(Created page with "= Introduction =")
 
Line 1: Line 1:
 
= Introduction =
 
= Introduction =
 +
This article represents the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].
 +
 +
= Objectives =
 +
The test process is focused on validating the data collected and on verifying the correctness functioning of GUI.
 +
 +
= Test Areas =
 +
The Toaster consists of two big components, as follows:
 +
 +
=== 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 ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and stop/start the toaster server])
 +
 +
=== Frontend ===
 +
 +
=== Functionality tests ===
 +
*  Manual testing in the first stage;
 +
*  Automate testing using  [http://www.seleniumhq.org/ 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);

Revision as of 07:37, 21 October 2013

Contents

Introduction

This article represents the test plan for Toaster.

Objectives

The test process is focused on validating the data collected and on verifying the correctness functioning of GUI.

Test Areas

The Toaster consists of two big components, as follows:

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

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