Toaster testing plan: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 38: Line 38:
*  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);


==== perf 2 ====
= Test Cycle =
 
{|class="wikitable" style="text-align: center;"
{|class="wikitable" style="text-align: center;"
| || || colspan="2" | Test execution cycle
| || || colspan="2" | Test execution cycle

Revision as of 07:46, 22 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 - 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);

Test Cycle

Test execution cycle
#Weekly Test #Full Pass Test
Build type Weekly Yes Yes
Build type #Backend Yes Yes
#Frontend Yes Yes
Target machine qemuarm Yes Yes
qemumips Yes
qemuppc Yes
qemux86 Yes Yes
Target image core-image-minimal Yes Yes
core-image-sato Yes