Difference between revisions of "QAAutomation"
(→About QA Automation) |
|||
(13 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
− | + | [[ru:RU/qaautomation]] | |
− | The OOo QA Automation Team has the main responsibility to assure stability and quality of the whole OOo/SUN Staroffice. The automated GUI testing provides a test framework with test scripts and an application ([[VCL TestTool]]) to test almost the whole office application automatically. The VCL TestTool scripts are written in BASIC with some additional functions especially for the office. The VCL TestTool communicates via TCP/IP with the office application. To start the GUI testing it is recommended to download the scripts (TestTool Environment) and the VCL TestTool application for the platform where you want to run the tests. [http://qa.openoffice.org/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomation.html home of automation team] for further details | + | [[sl:SL/QAAutomation]] |
+ | The OOo QA Automation Team has the main responsibility to assure stability and quality of the whole OOo/SUN Staroffice. The automated GUI testing provides a test framework with test scripts and an application ([[Testtool|VCL TestTool]]) to test almost the whole office application automatically. The VCL TestTool scripts are written in BASIC with some additional functions especially for the office. The VCL TestTool communicates via TCP/IP with the office application. To start the GUI testing it is recommended to download the scripts (TestTool Environment) and the VCL TestTool application for the platform where you want to run the tests. [http://qa.openoffice.org/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomation.html home of automation team] for further details | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | = QA Automation Alert Levels = | |
− | + | On this page you'll find an explanation of 'VTTDI'-Values (VCLTesttool defect index) generated by automated tests running on every master workspace. VTTDI is used on 'Quality Assurance Statuspage' ([[QUASTe]]) to assure a simple understanding of quality status. | |
+ | The VTTDI-Index is calculated by the following formula: <br>''''(warnings * 1 + errors * 3) / number of tests'''' | ||
+ | |||
+ | <TABLE border=1 width=100%> | ||
+ | <TR> | ||
+ | <TD BGCOLOR="green"><STRONG>Automation Quality status</STRONG>: green</TD> | ||
+ | </TR> | ||
+ | <TR><TD> | ||
+ | * Alert level: 1 ( VTTDI <= 0.3 ) | ||
+ | * release and category tests have been finished | ||
+ | * No critical issues have been found during automated tests | ||
+ | </TD></TR> | ||
+ | </TABLE> | ||
+ | |||
+ | <TABLE border=1 width=100%> | ||
+ | <TR> | ||
+ | <TD BGCOLOR="blue"><STRONG>Automation Quality status</STRONG>: lookout</TD> | ||
+ | </TR> | ||
+ | <TR><TD> | ||
+ | * Alert level: 2 ( VTTDI >=0.3 and <= 0.5 ) | ||
+ | * release and category tests have been finished | ||
+ | * Some errors and warnings have been found during automated testing | ||
+ | * Testresults must be evaluated by QA | ||
+ | * release might be at risk | ||
+ | </TD></TR> | ||
+ | </TABLE> | ||
+ | |||
+ | <TABLE border=1 width=100%> | ||
+ | <TR> | ||
+ | <TD BGCOLOR="#ffef00"><STRONG>Automation Quality status</STRONG>: mild</TD> | ||
+ | </TR> | ||
+ | <TR><TD> | ||
+ | * Alert level: 3 ( VTTDI > 0.5 and <= 1 ) | ||
+ | * release and category tests have been finished | ||
+ | * Some more errors and warnings have been found during automated testing | ||
+ | * Testresults must be evaluated by QA | ||
+ | * release is at risk | ||
+ | </TD></TR> | ||
+ | </TABLE> | ||
+ | |||
+ | <TABLE border=1 width=100%> | ||
+ | <TR> | ||
+ | <TD BGCOLOR="darkorange"><STRONG>Automation Quality status</STRONG>: moderate</TD> | ||
+ | </TR> | ||
+ | <TR><TD> | ||
+ | * Alert level: 4 ( VTTDI > 1 ) | ||
+ | * release and category tests have been finished | ||
+ | * Loads of errors and warnings have been found during automated testing | ||
+ | * Testresults must be evaluated by QA | ||
+ | * release is not possible | ||
+ | </TD></TR> | ||
+ | </TABLE> | ||
+ | |||
+ | <TABLE border=1 width=100%> | ||
+ | <TR> | ||
+ | <TD BGCOLOR="crimson"><STRONG>Automation Quality status</STRONG>: severe</TD> | ||
+ | </TR> | ||
+ | <TR><TD> | ||
+ | * Alert level: 5 ( VTTDI of any size ) | ||
+ | * release tests have not been finished | ||
+ | * Testresults must be evaluated by QA | ||
+ | * release is not possible | ||
+ | </TD></TR> | ||
+ | </TABLE> | ||
+ | |||
[[Category:Quality Assurance]] | [[Category:Quality Assurance]] |
Latest revision as of 21:27, 9 April 2010
The OOo QA Automation Team has the main responsibility to assure stability and quality of the whole OOo/SUN Staroffice. The automated GUI testing provides a test framework with test scripts and an application (VCL TestTool) to test almost the whole office application automatically. The VCL TestTool scripts are written in BASIC with some additional functions especially for the office. The VCL TestTool communicates via TCP/IP with the office application. To start the GUI testing it is recommended to download the scripts (TestTool Environment) and the VCL TestTool application for the platform where you want to run the tests. home of automation team for further details
QA Automation Alert Levels
On this page you'll find an explanation of 'VTTDI'-Values (VCLTesttool defect index) generated by automated tests running on every master workspace. VTTDI is used on 'Quality Assurance Statuspage' (QUASTe) to assure a simple understanding of quality status.
The VTTDI-Index is calculated by the following formula:
'(warnings * 1 + errors * 3) / number of tests'
Automation Quality status: green |
|
Automation Quality status: lookout |
|
Automation Quality status: mild |
|
Automation Quality status: moderate |
|
Automation Quality status: severe |
|