Extensible SDK Test Plan (eSDK): Difference between revisions
From Yocto Project
Jump to navigationJump to search
No edit summary |
|||
Line 1: | Line 1: | ||
[[Category: | [[Category:eSDK]] | ||
This article is the test plan for eSDK. | This article is the test plan for eSDK. | ||
Line 36: | Line 36: | ||
== Submitting Bugs == | == Submitting Bugs == | ||
Being part of the Yocto Project, eSDK follows the same Yocto Project guidelines and principles. The guidelines can be found at https://wiki.yoctoproject.org/wiki/Community_Guidelines. | Being part of the Yocto Project, eSDK follows the same Yocto Project guidelines and principles. The guidelines can be found at https://wiki.yoctoproject.org/wiki/Community_Guidelines. | ||
eSDK bugs are no different and are tracked into Bugzilla, the official Yocto Project bug tracker. Learn more about [https://wiki.yoctoproject.org/wiki/Bugzilla_Configuration_and_Bug_Tracking our process for reporting bugs]. | |||
=Requirements= | =Requirements= | ||
Line 82: | Line 82: | ||
= Test Areas = | = Test Areas = | ||
eSDK consists of two big components, as follows: | |||
== Backend == | == Backend == | ||
==== Functionality tests ==== | ==== 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/ | * [[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/eSDK-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 | * 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_eSDK.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 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 94: | Line 94: | ||
==== Usability tests ==== | ==== Usability tests ==== | ||
* Verify the easy usage of | * Verify the easy usage of eSDK ([https://wiki.yoctoproject.org/wiki/WebHob#Installation_and_Running easy to install and start/stop the eSDK server]) | ||
== Frontend == | == Frontend == | ||
Line 155: | Line 155: | ||
*; Objective: | *; Objective: | ||
** Ensure functionality of | ** Ensure functionality of eSDK component. | ||
== Release Test == | == Release Test == |
Revision as of 13:29, 19 May 2016
This article is the test plan for eSDK.
About eSDK
Objectives
Team members
QA Team involved in eSKDtesting
Francisco Pedraza
Scope
Test Strategy
Test automation
Test Approach
Sanity testing
Performance and Stress
Load testing
System Integration Testing
Regression
Maintaining the test cases
Submitting Bugs
Being part of the Yocto Project, eSDK follows the same Yocto Project guidelines and principles. The guidelines can be found at https://wiki.yoctoproject.org/wiki/Community_Guidelines. eSDK bugs are no different and are tracked into Bugzilla, the official Yocto Project bug tracker. Learn more about our process for reporting bugs.