Settings StateColorSettings/en: Unterschied zwischen den Versionen

Aus expecco Wiki (Version 2.x)
Zur Navigation springen Zur Suche springen
Zeile 2: Zeile 2:


This dialog allows for the status colors (in lists and reports) to be choosen.
This dialog allows for the status colors (in lists and reports) to be choosen.
<br>By default, the colors are:
By default, the colors are:


* '''Green'''
;Green
:successful test runs / test items.
: successful test runs / test items.


* '''Red'''
;Red
:for failed test runs / test items.<BR>A failure should be reported if the System-Under-Test (SUT) is incorrect. This verdict is the outcome of a test which detects a malfunction in the system under test. It is NOT reported if the test itself is erronous (i.e. raises an exception).<BR><B>A failure-result requires action by the developer of the System-Under-Test.</B>
: for failed test runs / test items. A failure should be reported if the System-Under-Test (SUT) is incorrect. This verdict is the outcome of a test which detects a malfunction in the system under test. It is NOT reported if the test itself is erroneous (i.e. raises an exception).
: '''A failure-result requires action by the developer of the System-Under-Test'''.


* '''Dark Red'''
;Dark Red
:for erronous test runs / test items.<BR>An error is reported if the Test itself is malfunctioning. This means, that during the test execution an unhandled error/exception was raised, and therefore, we do not know if the System-Under-Test (SUT) is correct.<BR><B>An error-result always requires action by the test-developer</B>.
: for erroneous test runs / test items. An error is reported if the test itself is malfunctioning. This means, that during the test execution an unhandled error/exception was raised, and therefore, we do not know if the System-Under-Test (SUT) is correct.
: '''An error-result always requires action by the test-developer'''.


* '''Grey'''
;Grey
:for inconclusive test runs / test items. The term <DFN>"inconclusive"</DFN> means, that for some reason, the test could not be executed (typically due to missing resources, measurement devices, databases etc.), and therefore, it is not known, if the System-Under-Test (SUT) functions correctly or not. Also, skipped and aborted tests are marked as inconclusive. <BR><B>An inconclusive-result requires action by the test-manager</B>.
:for inconclusive test runs / test items. The term <DFN>"inconclusive"</DFN> means, that for some reason, the test could not be executed (typically due to missing resources, measurement devices, databases etc.), and therefore, it is not known, if the System-Under-Test (SUT) functions correctly or not. Also, skipped and aborted tests are marked as inconclusive.
: '''An inconclusive-result requires action by the test-manager'.


If you have red/green visibility problems,
If you have red/green visibility problems,
you may want to change the setting for better readability.
you may want to change the setting for better readability.


[[Category:Settings]]

Back to [[SettingsDialog/en | Settings Dialog]].

Version vom 7. April 2014, 18:17 Uhr

State Colors Settings[Bearbeiten]

This dialog allows for the status colors (in lists and reports) to be choosen. By default, the colors are:

Green
successful test runs / test items.
Red
for failed test runs / test items. A failure should be reported if the System-Under-Test (SUT) is incorrect. This verdict is the outcome of a test which detects a malfunction in the system under test. It is NOT reported if the test itself is erroneous (i.e. raises an exception).
A failure-result requires action by the developer of the System-Under-Test.
Dark Red
for erroneous test runs / test items. An error is reported if the test itself is malfunctioning. This means, that during the test execution an unhandled error/exception was raised, and therefore, we do not know if the System-Under-Test (SUT) is correct.
An error-result always requires action by the test-developer.
Grey
for inconclusive test runs / test items. The term "inconclusive" means, that for some reason, the test could not be executed (typically due to missing resources, measurement devices, databases etc.), and therefore, it is not known, if the System-Under-Test (SUT) functions correctly or not. Also, skipped and aborted tests are marked as inconclusive.
An inconclusive-result requires action by the test-manager'.

If you have red/green visibility problems, you may want to change the setting for better readability.



Copyright © 2014-2024 eXept Software AG