Test Case/en - Versionsgeschichte

Cg: /* Defining a Test Action */

2023-07-20T13:01:44Z

Defining a Test Action

← Nächstältere Version		Version vom 20. Juli 2023, 13:01 Uhr
Zeile 24:		Zeile 24:
	The right editor pane now presents the various aspects of the action:		The right editor pane now presents the various aspects of the action:
	* [[Scheme_Editor/en\|"''Scheme''"]] which shows the ''outside or external view'' (the scheme) of the action		* [[Scheme_Editor/en\|"''Scheme''"]] which shows the ''outside or external view'' (the scheme) of the action
	* "''Network''" which shows the inner workings (the ''implementation'')		* [[Compound_Network_Editor/en\|"''Network''"]] which shows the inner workings (the ''implementation'')
	* "''Environment''" contains local variables of the action (if needed)		* "''Environment''" contains local variables of the action (if needed)
	* "''Test/Demo''" contains a setup to the run this action in isolation		* "''Test/Demo''" contains a setup to the run this action in isolation

Cg: /* Defining a Test Action */

2023-07-20T12:58:26Z

Defining a Test Action

← Nächstältere Version		Version vom 20. Juli 2023, 12:58 Uhr
Zeile 23:		Zeile 23:
	Select the "''New Compound Action''" menu function (and give it a better name).		Select the "''New Compound Action''" menu function (and give it a better name).
	The right editor pane now presents the various aspects of the action:		The right editor pane now presents the various aspects of the action:
	* "''~~Schema~~''" which shows the ''outside or external view'' of the action		* [[Scheme_Editor/en\|"''Scheme''"]] which shows the ''outside or external view'' (the scheme) of the action
	* "''Network''" which shows the inner workings (the ''implementation'')		* "''Network''" which shows the inner workings (the ''implementation'')
	* "''Environment''" contains local variables of the action (if needed)		* "''Environment''" contains local variables of the action (if needed)

Cg: /* Creating the Test Plan */

2023-07-20T12:57:16Z

Creating the Test Plan

← Nächstältere Version		Version vom 20. Juli 2023, 12:57 Uhr
Zeile 14:		Zeile 14:

	[[Datei:TestCaseExample2.png\|thumb\|150px\|New test plan shown]]		[[Datei:TestCaseExample2.png\|thumb\|150px\|New test plan shown]]
	Once created, the [[Testplan ~~Editor-TestplanListView~~ Editor/en\|''testplan editor'']] at the right is showing the test plan's attributes (scroll the right bottom pane down to see them all).		Once created, the [[Testplan Editor/en\|''testplan editor'']] at the right is showing the test plan's attributes (scroll the right bottom pane down to see them all).
	Initially, the list of test cases is empty.		Initially, the list of test cases is empty.

Cg: /* Creating the Test Plan */

2023-07-20T12:55:34Z

Creating the Test Plan

← Nächstältere Version		Version vom 20. Juli 2023, 12:55 Uhr
Zeile 14:		Zeile 14:

	[[Datei:TestCaseExample2.png\|thumb\|150px\|New test plan shown]]		[[Datei:TestCaseExample2.png\|thumb\|150px\|New test plan shown]]
	Once created, the ~~test~~ ~~plan~~ editor at the right is showing the test plan's attributes (scroll the right bottom pane down to see them all).		Once created, the [[Testplan Editor-TestplanListView Editor/en\|''testplan editor'']] at the right is showing the test plan's attributes (scroll the right bottom pane down to see them all).
	Initially, the list of test cases is empty.		Initially, the list of test cases is empty.

Cg: Cg verschob die Seite Test case/en nach Test Case/en

2023-07-20T12:53:11Z

Cg verschob die Seite Test case/en nach Test Case/en

← Nächstältere Version	Version vom 20. Juli 2023, 12:53 Uhr
(kein Unterschied)

Cg: /* Required vs. Optional Test Cases */

2023-07-20T12:52:16Z

Required vs. Optional Test Cases

← Nächstältere Version		Version vom 20. Juli 2023, 12:52 Uhr
Zeile 103:		Zeile 103:
	You should leave them as "''required''", if it does not make sense to try any folloup tests on a failure (for example, if a login or power up sequence fails), and "''optional''" if the tests are independent of previous outcomes.		You should leave them as "''required''", if it does not make sense to try any folloup tests on a failure (for example, if a login or power up sequence fails), and "''optional''" if the tests are independent of previous outcomes.

	[[Datei:TestCaseExample9.png\|thumb\|150px\|~~Obligatory~~ vs. Optional]]		[[Datei:TestCaseExample9.png\|thumb\|150px\|Required vs. Optional]]
	Try to change the settings. You can also select multiple test case items and use the roght-click menu function "''Selection''" → "''Make Optional Testcase''" to change multiple items with one click.		Try to change the settings. You can also select multiple test case items and use the roght-click menu function "''Selection''" → "''Make Optional Testcase''" to change multiple items with one click.

Cg: /* Multiple Test Cases using the same Test Action */

2023-07-20T12:52:02Z

Multiple Test Cases using the same Test Action

← Nächstältere Version		Version vom 20. Juli 2023, 12:52 Uhr
Zeile 94:		Zeile 94:

	Then run the test plan again.		Then run the test plan again.

			=== Required vs. Optional Test Cases ===

	If both entered filenames exist, you'll get a successful (green) result.		If both entered filenames exist, you'll get a successful (green) result.

Cg: /* Multiple Test Cases using the same Test Action */

2023-07-20T12:50:25Z

Multiple Test Cases using the same Test Action

← Nächstältere Version		Version vom 20. Juli 2023, 12:50 Uhr
Zeile 99:		Zeile 99:
	If the first file does not exist, the test plan stops after the failing test case, not executing further steps. This behavior is controlled by the ''Mandatory'' choice, which can be either "''required''" or "''optional''". "''Required''" is the default, and means that a successful outcome of that test is a prerequisite for further tests. "''Optional''" means that followup tests should still be executed, even if that test fails.		If the first file does not exist, the test plan stops after the failing test case, not executing further steps. This behavior is controlled by the ''Mandatory'' choice, which can be either "''required''" or "''optional''". "''Required''" is the default, and means that a successful outcome of that test is a prerequisite for further tests. "''Optional''" means that followup tests should still be executed, even if that test fails.

	You should leave them as ''required'', if it does not make sense to try any folloup tests on a failure (for example, if a login or power up sequence fails), and ''optional'' if the tests are independent of ~~rpevious~~ outcomes.		You should leave them as "''required''", if it does not make sense to try any folloup tests on a failure (for example, if a login or power up sequence fails), and "''optional''" if the tests are independent of previous outcomes.

	[[Datei:TestCaseExample9.png\|thumb\|150px\|Obligatory vs. Optional]]		[[Datei:TestCaseExample9.png\|thumb\|150px\|Obligatory vs. Optional]]

Cg: /* Multiple Test Cases using the same Test Action */

2023-07-20T12:49:57Z

Multiple Test Cases using the same Test Action

← Nächstältere Version		Version vom 20. Juli 2023, 12:49 Uhr
Zeile 97:		Zeile 97:
	If both entered filenames exist, you'll get a successful (green) result.		If both entered filenames exist, you'll get a successful (green) result.

	If the first file does not exist, the test plan stops after the failing test case, not executing further steps. This behavior is controlled by the ''Mandatory'' choice, which can be either ''required'' or ''optional''. ''Required'' is the default, and means that a successful outcome of that test is a prerequisite for further tests. ''Optional'' means, that followup tests should still be executed, even if that test fails.		If the first file does not exist, the test plan stops after the failing test case, not executing further steps. This behavior is controlled by the ''Mandatory'' choice, which can be either "''required''" or "''optional''". "''Required''" is the default, and means that a successful outcome of that test is a prerequisite for further tests. "''Optional''" means that followup tests should still be executed, even if that test fails.

	You should leave them as ''required'', if it does not make sense to try any folloup tests on a failure (for example, if a login or power up sequence fails), and ''optional'' if the tests are independent of rpevious outcomes.		You should leave them as ''required'', if it does not make sense to try any folloup tests on a failure (for example, if a login or power up sequence fails), and ''optional'' if the tests are independent of rpevious outcomes.

Cg: /* Multiple Test Cases using the same Test Action */

2023-07-20T12:49:14Z

Multiple Test Cases using the same Test Action

← Nächstältere Version		Version vom 20. Juli 2023, 12:49 Uhr
Zeile 97:		Zeile 97:
	If both entered filenames exist, you'll get a successful (green) result.		If both entered filenames exist, you'll get a successful (green) result.

	If the first file does not exist, the test plan stops after the failing test case, not executing further steps. This behavior is controlled by the ''~~priority~~'' choice, which can be either ''~~obligatory~~'' or ''optional''. ''~~Obligatory~~'' is the default, and means that a successful outcome of that test is a prerequisite for further tests. ''Optional'' means, that followup tests should still be executed, even if that test fails.		If the first file does not exist, the test plan stops after the failing test case, not executing further steps. This behavior is controlled by the ''Mandatory'' choice, which can be either ''required'' or ''optional''. ''Required'' is the default, and means that a successful outcome of that test is a prerequisite for further tests. ''Optional'' means, that followup tests should still be executed, even if that test fails.

	You should leave them as ''~~obligatory~~'', if it does not make sense to try any folloup tests on a failure (for example, if a login or power up sequence fails), and ''optional'' if the tests are independent of rpevious outcomes.		You should leave them as ''required'', if it does not make sense to try any folloup tests on a failure (for example, if a login or power up sequence fails), and ''optional'' if the tests are independent of rpevious outcomes.

	[[Datei:TestCaseExample9.png\|thumb\|150px\|Obligatory vs. Optional]]		[[Datei:TestCaseExample9.png\|thumb\|150px\|Obligatory vs. Optional]]