Yocto Project - User contributions [en]

Toaster testing plan

2014-03-26T11:43:53Z

Proca Andreea Brandusa: /* Functionality tests */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning incomplete (fields having null values) or wrong data for a certain set of entries from each table - our goal is to have 90% data collected. The tests can be found [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=andreeap/toaster-tests&id=7cfd179be5db2a5530d60093fd09d0240138c2fa here];
* Calculation of the data collection rate - the ratio between the number of the variables having null values and the total number of variables collected (the data collection rate does not include wrong values); Run: ./fail_rate.py path_to_toaster.sqlite_file. Output: table_name field_name value_that_never_changes and for each table a percentage: (the number of occurences of all the fields that never change their values)/(total number of entries for that table);
* 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 by verifying most of the values from the database by connecting directly to the database - our immediate goal is to have 90% correct data collected;

==== Usability tests ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2014-03-26T11:42:47Z

Proca Andreea Brandusa: /* Functionality tests */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning incomplete (fields having null values) or wrong data for a certain set of entries from each table - our goal is to have 90% data collected. The tests can be found [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=andreeap/toaster-tests&id=7cfd179be5db2a5530d60093fd09d0240138c2fa here];
* Calculation of the data collection rate - the ratio between the number of the variables having null values and the total number of variables collected (the data collection rate does not include wrong values); When running, the user has to give as parameter the path to toaster.sqlite file. Output: table_name field_name value_that_never_changes and for each table a percentage: (the number of occurences of all the fields that never change their values)/(total number of entries for that table);
* 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 by verifying most of the values from the database by connecting directly to the database - our immediate goal is to have 90% correct data collected;

==== Usability tests ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2014-01-15T12:09:09Z

Proca Andreea Brandusa: /* Functionality tests */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning incomplete (fields having null values) or wrong data for a certain set of entries from each table - our goal is to have 90% data collected. The tests can be found [http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=andreeap/toaster-tests&id=7cfd179be5db2a5530d60093fd09d0240138c2fa here];
* Calculation of the data collection rate - the ratio between the number of the variables having null values and the total number of variables collected (the data collection rate does not include wrong values);
* 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 by verifying most of the values from the database by connecting directly to the database - our immediate goal is to have 90% correct data collected;

==== Usability tests ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-11-29T14:03:33Z

Proca Andreea Brandusa: /* Test Cycle */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning incomplete data (fields having null values) - our goal is to have 100% data collected;
* Calculation of the data collection rate - the ratio between the number of the variables having null values and the total number of variables collected (the data collection rate does not include wrong values);
* 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 by verifying most of the values from the database by connecting directly to the database - our immediate goal is to have 90% correct data collected;

==== Usability tests ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-11-28T10:40:57Z

Proca Andreea Brandusa: /* Functionality tests */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning incomplete data (fields having null values) - our goal is to have 100% data collected;
* Calculation of the data collection rate - the ratio between the number of the variables having null values and the total number of variables collected (the data collection rate does not include wrong values);
* 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 by verifying most of the values from the database by connecting directly to the database - our immediate goal is to have 90% correct data collected;

==== Usability tests ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-11-28T10:40:41Z

Proca Andreea Brandusa: /* Functionality tests */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning incomplete data (fields having null values) - our goal is to have 100% data collected;;
* Calculation of the data collection rate - the ratio between the number of the variables having null values and the total number of variables collected (the data collection rate does not include wrong values);
* 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 by verifying most of the values from the database by connecting directly to the database - our immediate goal is to have 90% correct data collected;

==== Usability tests ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-31T12:01:02Z

Proca Andreea Brandusa: /* Functionality tests */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning incomplete data (fields having null values);
* Calculation of the data collection rate - the ratio between the number of the variables having null values and the total number of variables collected (the data collection rate does not include wrong values);
* 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 by verifying most of the values from the database by connecting directly to the database - our immediate goal is to have 80% correct data collected;

==== Usability tests ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-30T12:18:42Z

Proca Andreea Brandusa: /* Functionality tests */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning incomplete data (fields having null values);
* Calculation of the data collection rate - the ratio between the number of the variables having null values and the total number of variables collected (the data collection rate does not include wrong values);
* 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 by verifying most of the values from the database by connecting directly to the database;

==== Usability tests ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-30T12:17:25Z

Proca Andreea Brandusa: /* Functionality tests */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning incomplete data (fields having null values);
* Calculation of the data collection rate - the ratio between the number of the variables having null values and the total number of variables collected (the data collection rate does not include wrong values);
* 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 by verifying directly most of the values from the database;

==== Usability tests ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-30T12:15:52Z

Proca Andreea Brandusa: /* Functionality tests */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning incomplete data (fields having null values);
* Calculation of the data collection rate - the ratio between the number of the variables having null values and the total number of variables collected (the data collection rate does not include wrong values);
* 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 by verifying directly some of the values from the database;

==== Usability tests ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-30T12:15:27Z

Proca Andreea Brandusa: /* Backend */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning incomplete data (fields having null values);
* Calculation of the data collection rate - the ratio between the number of the variables having null values and the total number of variables collected (the data collection rate does not include the wrong values);
* 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 by verifying directly some of the values from the database;

==== Usability tests ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-22T13:48:04Z

Proca Andreea Brandusa: /* Functionality tests */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | REST API]] verification – create Django tests to detect API calls returning no data;
* Calculation of the data collection rate - the ratio between 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 ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-22T13:12:45Z

Proca Andreea Brandusa:

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | 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 ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="5" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| qemux86-64 || || || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-22T10:01:16Z

Proca Andreea Brandusa: /* Usability tests */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | 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 ====
* Verify the easy usage of Toaster ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="4" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-22T08:52:10Z

Proca Andreea Brandusa: /* Objectives */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob Toaster].

= Objectives =
The test process focuses on:

* validating the data collected from the build process;
* verifying the correct functioning of the Toaster GUI; TBD

= Test Areas =
Toaster consists of two big components, as follows:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | 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 ====
* Verify the easy usage of 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="4" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-22T08:46:47Z

Proca Andreea Brandusa: /* Compatibility tests */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob 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:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | 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 ====
* Verify the easy usage of 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; TBD

==== Usability tests ====
* Verify if the GUI design is as described here: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="4" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-22T08:20:10Z

Proca Andreea Brandusa:

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob 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:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | 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 ====
* Verify the easy usage of 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: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="3" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="4" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-22T08:18:02Z

Proca Andreea Brandusa:

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob 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:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | 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 ====
* Verify the easy usage of 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: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="2" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="4" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full Pass Test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-22T08:17:34Z

Proca Andreea Brandusa:

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob 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:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | 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 ====
* Verify the easy usage of 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: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="2" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="4" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

== Release Test ==
*; Scope:
** Release candidates that pass [[#Full pass test]]

*; Objective:
** All scheduled features are covered, or rescheduled;
** All relevant bugs are fixed and verified.

Toaster testing plan

2013-10-22T08:16:35Z

Proca Andreea Brandusa: /* Test Cycle */

= Introduction =
This article is the test plan for [https://wiki.yoctoproject.org/wiki/WebHob 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:

== Backend ==

==== Functionality tests ====
* [[REST_API_Contracts | 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 ====
* Verify the easy usage of 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: http://yoctoproject.org/webhob;
* Friendly graphical user interface;

==== Performance tests ====
* Stress testing (e.g. display appropriate error messages when the system is under stress);

= Test Cycle =
{|class="wikitable" style="text-align: center;"
| || || colspan="2" | Test execution cycle
|-
| || || [[#Weekly Test]] || [[#Full Pass Test]] || [[#Release Test]]
|-
| rowspan="2" | Build type || Weekly || Yes || Yes ||
|-
| Release || Yes || Yes || Yes
|-
| rowspan="2" | [[#Test Areas]] || [[#Backend]] || Yes || Yes || Yes
|-
| [[#Frontend]] || Yes || Yes || Yes
|-
| rowspan="4" | Target machine || qemuarm || || Yes || Yes
|-
| qemumips|| || || Yes
|-
| qemuppc|| || || Yes
|-
| qemux86|| Yes || Yes || Yes
|-
| rowspan="3" | Target image|| core-image-minimal|| Yes || Yes ||
|-
| core-image-sato-sdk|| || Yes || Yes
|}

== Weekly Test ==
*; Scope:
** Images built weekly and released through the distribution team.

*; Objective:
** Functionality test on most areas with minimum sets of tests;
** Regression test with high probability to find bugs.

== Full Pass Test ==
*; Scope:
** Images built as candidates for milestone or final release;
** Passed [[#Weekly Test]]

*; Objective:
** Ensure functionality of Toaster component.

Toaster testing plan

2013-10-22T08:02:16Z

Proca Andreea Brandusa:

Toaster testing plan

2013-10-22T08:00:47Z

Proca Andreea Brandusa:

Toaster testing plan

2013-10-22T08:00:17Z

Proca Andreea Brandusa:

Toaster testing plan

2013-10-22T07:58:05Z

Proca Andreea Brandusa:

Toaster testing plan

2013-10-22T07:56:54Z

Proca Andreea Brandusa:

Toaster testing plan

2013-10-22T07:46:49Z

Proca Andreea Brandusa: /* perf 2 */

Toaster testing plan

2013-10-22T07:46:36Z

Proca Andreea Brandusa: /* Performance tests */

Toaster testing plan

2013-10-22T07:44:47Z

Proca Andreea Brandusa: /* perf 2 */

Toaster testing plan

2013-10-22T07:31:49Z

Proca Andreea Brandusa: /* perf 2 */

Toaster testing plan

2013-10-22T07:25:51Z

Proca Andreea Brandusa:

Toaster testing plan

2013-10-22T07:22:20Z

Proca Andreea Brandusa:

Toaster testing plan

2013-10-21T15:05:15Z

Proca Andreea Brandusa:

Toaster testing plan

2013-10-21T14:41:52Z

Proca Andreea Brandusa: /* Test Areas */

= Introduction =
This article is 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);

Toaster testing plan

2013-10-21T14:41:31Z

Proca Andreea Brandusa: /* Backend */

Toaster testing plan

2013-10-21T14:41:15Z

Proca Andreea Brandusa: /* Frontend */

Toaster testing plan

2013-10-21T14:38:18Z

Proca Andreea Brandusa: /* Usability tests */

Toaster testing plan

2013-10-21T14:37:32Z

Proca Andreea Brandusa: /* Introduction */

= Introduction =
This article is 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);

Toaster testing plan

2013-10-21T14:37:13Z

Proca Andreea Brandusa:

= 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);

Toaster testing plan

2013-10-21T13:15:15Z

Proca Andreea Brandusa: Created page with "= Introduction ="

= Introduction =