Settings StateColorSettings/en: Unterschied zwischen den Versionen

Aus expecco Wiki (Version 2.x)
Zur Navigation springen Zur Suche springen
 
(32 dazwischenliegende Versionen von 3 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
== State Colors Settings ==
== State Colors Settings ==


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 chosen.
<br>By default, the colors are:


You find these under "''Extras''" &#8594; "''Settings''" &#8594; "''[[Settings_LookAndFeelSettings/en|Look & Feel]]''" &#8594; "''State Colors''".
* '''Green'''
:successful test runs / test items.


==== Default State Colors ====
* '''Red'''
A description of the colors and their meanings is also found in "[[Test_Editor/en#State_Colors|State Colors]]" and verdicts are described in the "[[Glossary/en#Verdict|Glossary]]".
:for failed test runs / test items.<BR>A failure should be reported if the System-Under-Test (SUT) is incorrect.<BR><B>A failure-result requires action by the developer of the System-Under-Test.</B>
<br>By default, the colors for test outcomes in the UI and reports are:


;Green
* '''Dark Red'''
:for erronous test runs / test items.
: ("''Pass''") successful test runs / test items.
<BR>An error is reported if the Test itself is malfunctioning.
This means, that 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>.


;Red
* '''Grey'''
: ("''Fail''") for failed test runs / test items. A failure should be reported if the [[Glossary/en#SUT_.28System_Under_Test.29|System-Under-Test (SUT) ]] is incorrect. This [[Glossary/en#Verdict|verdict]] is the outcome of a test which detects a malfunction in the SUT (NOT if the test itself is erroneous, for example an exception, such as division by zero).
:for inconclusive test runs / test items.
: A failure-result requires action by the developer of the System-Under-Test.
The term <DFN>"inconclusive"</DFN> means, that for some reason, the test could not be executed

(typically due to
;Dark Red
missing resources, measurement devices, databases etc.),
: ("''Error''") 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 [[Glossary/en#SUT_.28System_Under_Test.29|SUT]] is correct.
and therefore, it is not known, if the System-Under-Test (SUT) is correct or not.
: An error-result requires action by the test-developer.
Also, skipped tests are marked as inconclusive.

<BR><B>An inconclusive-result requires action by the test-manager</B>.
;Grey
: ("''Inconclusive''") 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, power down, server down etc.), and therefore, it is not known, if the [[Glossary/en#SUT_.28System_Under_Test.29|SUT]] functions correctly or not. Also, skipped and aborted tests are marked as inconclusive.
: An inconclusive-result requires action by the test-manager.

Additional colors are used for individual steps in a network diagram, to indicate if warning messages were generated or if exceptions were handled during the execution. Also a dfferent grey colors are used for skipped actions.


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.
<br>Japanese users may prefer blue instead of green.
<br>Old fashioned, die-hard-communists may want to exchange red and green &#9786;.

&nbsp;

<hr>

Back to [[Settings_LookAndFeelSettings/en | Look & Feel Settings]]

[[Category:Settings]]

Aktuelle Version vom 29. April 2025, 23:55 Uhr

State Colors Settings[Bearbeiten]

This dialog allows for the status colors (in lists and reports) to be chosen.

You find these under "Extras" → "Settings" → "Look & Feel" → "State Colors".

Default State Colors[Bearbeiten]

A description of the colors and their meanings is also found in "State Colors" and verdicts are described in the "Glossary".
By default, the colors for test outcomes in the UI and reports are:

Green
("Pass") successful test runs / test items.
Red
("Fail") 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 SUT (NOT if the test itself is erroneous, for example an exception, such as division by zero).
A failure-result requires action by the developer of the System-Under-Test.
Dark Red
("Error") 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 SUT is correct.
An error-result requires action by the test-developer.
Grey
("Inconclusive") 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, power down, server down etc.), and therefore, it is not known, if the SUT functions correctly or not. Also, skipped and aborted tests are marked as inconclusive.
An inconclusive-result requires action by the test-manager.

Additional colors are used for individual steps in a network diagram, to indicate if warning messages were generated or if exceptions were handled during the execution. Also a dfferent grey colors are used for skipped actions.

If you have red/green visibility problems, you may want to change the setting for better readability.
Japanese users may prefer blue instead of green.
Old fashioned, die-hard-communists may want to exchange red and green ☺.

 


Back to Look & Feel Settings



Copyright © 2014-2024 eXept Software AG