Manual Test Tutorial/en - Versionsgeschichte

Matilk: /* Creating and Using own GUI Layouts */

2023-08-28T16:32:46Z

Creating and Using own GUI Layouts

← Nächstältere Version		Version vom 28. August 2023, 16:32 Uhr
Zeile 302:		Zeile 302:
	[[Datei:Manual Test 30.png\|800px\|''MT - TestStep with Expected'' as example how to create a customized GUI]]		[[Datei:Manual Test 30.png\|800px\|''MT - TestStep with Expected'' as example how to create a customized GUI]]

	The block ''MT - GUI TestStep+'' provides both predefined aspects at the top pins (for them there are also basic blocks to determine their values) and an unlimited number of aspects you can add through the [[DiagramElements-Pin/en#Variable_Number_of_Pins\|variable pin group]] at the end. The output pin ''infoValues'' returns a Dictionary containing all the aspects that where set and their values. You can use this		The block ''MT - GUI TestStep+'' provides both predefined aspects at the top pins (for them there are also basic blocks to determine their values) and an unlimited number of aspects you can add through the [[DiagramElements-Pin/en#Variable_Number_of_Pins\|variable pin group]] at the end. The output pin ''infoValues'' returns a Dictionary containing all the aspects that where set and their values. You can use this to get the values of user inputs from the GUI.


Zeile 319:		Zeile 319:
	* '''Images'''		* '''Images'''
	: There are several possibilities to add images to your GUI. You can use Label and its Label Holder to your image. That is suitable for small icon-like images. For larger images you can use an ArbitraryComponent with an ImageView. In the Widget Gallery you find it under ''Embed''. There is a scrollable and a non-scrollable variant of this widget. Set the ''Model'' to your image and ''View / Class'' to <code>ImageView</code>, both in the ''Basics'' tab.		: There are several possibilities to add images to your GUI. You can use Label and its Label Holder to your image. That is suitable for small icon-like images. For larger images you can use an ArbitraryComponent with an ImageView. In the Widget Gallery you find it under ''Embed''. There is a scrollable and a non-scrollable variant of this widget. Set the ''Model'' to your image and ''View / Class'' to <code>ImageView</code>, both in the ''Basics'' tab.
	: As a use case take a look at ''MT - TestStep with Image Preview''. For this ~~testcase~~ there are also some callbacks defined, to further adjust the appearance some components, but do not worry, if you don't understand it, you do not necessarily need them.		: As a use case take a look at ''MT - TestStep with Image Preview''. For this teststep there are also some callbacks defined, to further adjust the appearance some components, but do not worry, if you don't understand it, you do not necessarily need them.
	: [[Datei:Manual Test 32.png\|800px\|Image with ArbitraryComponent]]		: [[Datei:Manual Test 32.png\|800px\|Image with ArbitraryComponent]]

Matilk: /* Manual TestStep (MarkDown) */

2023-08-28T14:49:25Z

Manual TestStep (MarkDown)

← Nächstältere Version		Version vom 28. August 2023, 14:49 Uhr
Zeile 283:		Zeile 283:

	* '''Text formatting'''		* '''Text formatting'''
			** Italic (<code>*</code>):
⚫	** ~~Italic (~~<code>~~</code>): <br><code>~~</code>''text''<code>*</code> or <code>_</code>''text''<code>_</code>: Text is shown in italics.
	~~Bold (~~<code>~~</code>): <br><code>~~</code>''text''<code>**</code> or <code>__</code>''text''<code>__</code>: Text is shown in ~~bold~~.		: <code></code>''text''<code>*</code> or <code>_</code>''text''<code>_</code>: Text is shown in ''italics''.
			Bold (<code></code>):
	Italic and Bold (<code></code>)<br><code></code>''text''<code>*</code> or <code>___</code>''text''<code>___</code>: Text is shown in italics and bold.
	** ~~Code (~~<code>`</code>)<br><code>`</code>''text''<code>`</code>: Text is shown as ~~code~~.		: <code></code>''text''<code>*</code> or <code>__</code>''text''<code>__</code>: Text is shown in '''bold'''.
			Italic and Bold (<code>*</code>)
		⚫	: <code></code>''text''<code>*</code> or <code>___</code>''text''<code>___</code>: Text is shown in '''''italics and bold'''''.
			** Code (<code>`</code>)
			*: <code>`</code>''text''<code>`</code>: Text is shown as <code>code</code>.

	All other lines are left unformatted,		All other lines are left unformatted,

Matilk: /* Manual Test Wizard – Start */

2023-08-28T14:37:06Z

Manual Test Wizard – Start

@@ Zeile 173: / Zeile 173: @@
 InputPin Parameter:
-* '''origin''':<br>defines the upper-left corner of of the wizard window in pixel coordinates on the screen. It should be given as a Point instance with x/y coordinates.<br>Example: <code>20@40</code> means 20 pixel from the left, 40 pixel from top origin of the screen<br>(you can also write <code>Point x:20 y:40</code> as an alternative).
+: defines the upper-left corner of of the wizard window in pixel coordinates on the screen. It should be given as a Point instance with x/y coordinates.
 == Manual Test Wizard – Preset Values ==

Matilk: /* Manual Test Action Library */ section levels

2023-08-28T13:01:08Z

Manual Test Action Library: section levels

Matilk: /* Orders on What to Do in Test Step */

2023-08-28T12:57:03Z

Orders on What to Do in Test Step

← Nächstältere Version		Version vom 28. August 2023, 12:57 Uhr
Zeile 74:		Zeile 74:
	Depending on how the test step was defined, this can be presented as simple plain text, or in a more appealing HTML presentation. See more on this in the documentation on the [[#Manual_TestStep_.28API.29\|Manual TestStep API]] below.		Depending on how the test step was defined, this can be presented as simple plain text, or in a more appealing HTML presentation. See more on this in the documentation on the [[#Manual_TestStep_.28API.29\|Manual TestStep API]] below.

	Simple Plaintext ~~presentation~~:		Simple Plaintext Presentation:
	<br>[[Datei:Manual Test 6.png\|300px]]		<br>[[Datei:Manual Test 6.png\|300px]]

Matilk: /* Orders on What to Do in Test Step */ Link to Manual TestStep API

2023-08-28T12:56:23Z

Orders on What to Do in Test Step: Link to Manual TestStep API

← Nächstältere Version		Version vom 28. August 2023, 12:56 Uhr
Zeile 72:		Zeile 72:
	The wizard's lower area present the test step's description.		The wizard's lower area present the test step's description.

	Depending on how the test step was defined, this can be presented as simple plain text, or in a more appealing HTML presentation. See more on this in the ~~''Standard~~ ~~Teststep''~~ ~~doc~~ below.		Depending on how the test step was defined, this can be presented as simple plain text, or in a more appealing HTML presentation. See more on this in the documentation on the [[#Manual_TestStep_.28API.29\|Manual TestStep API]] below.

	Simple Plaintext presentation:		Simple Plaintext presentation:

Matilk: /* Informationen on the Current Step */

2023-08-28T11:35:05Z

Informationen on the Current Step

← Nächstältere Version		Version vom 28. August 2023, 11:35 Uhr
Zeile 47:		Zeile 47:
	The other buttons are used to attach files or screenshots.		The other buttons are used to attach files or screenshots.

	== ~~Informationen~~ on the ~~current~~ ~~step~~ ==		== Information on the Current Step ==
	This area ~~show~~ the current step's name, the test case, of which it is part of, and the test plan which is currently running. Some of this depends on whether the action is executed as part of a test plan, or as a single-action run (in the "~~test~~/~~demo~~" tab of the editor). This needs proper tagging of your blocks as ''TEST-CASE'' and ''TEST-STEP'' to work (see next section).		This area shows the current step's name, the test case, of which it is part of, and the test plan which is currently running. Some of this depends on whether the action is executed as part of a test plan, or as a single-action run (in the "Test/Demo" tab of the editor). This needs proper tagging of your blocks as ''TEST-CASE'' and ''TEST-STEP'' to work (see next section).

	[[Datei:Manual Test 2.png\|Manual Test Info Bar]]		[[Datei:Manual Test 2.png\|Manual Test Info Bar]]


	== Test Step vs. Test Case ==		== Test Step vs. Test Case ==

Matilk: /* The Toolbar */

2023-08-28T11:26:09Z

The Toolbar

← Nächstältere Version		Version vom 28. August 2023, 11:26 Uhr
Zeile 42:		Zeile 42:
	The toolbar provides functions to set the outcome of the current step, to add comments and to attach data files or screenshots to the report.		The toolbar provides functions to set the outcome of the current step, to add comments and to attach data files or screenshots to the report.

	Of special relevance are the ~~next~~ buttons (triangular right arrows); these confirm the current step and mark it as "''Successful''" (green), "''Failed''" (red) or "''Inconclusive''" (gray).		Of special relevance are the "Next" buttons (triangular right arrows); these confirm the current step and mark it as "''Successful''" (green), "''Failed''" (red) or "''Inconclusive''" (gray).
	The yellow button also stands for "''Success''", but asks for a comment to be added as warning to the final report and log file.		The yellow button also stands for "''Success''", but asks for a comment to be added as warning to the final report and log file.

Matilk: /* The Toolbar */

2023-08-28T11:25:25Z

The Toolbar

← Nächstältere Version		Version vom 28. August 2023, 11:25 Uhr
Zeile 40:		Zeile 40:

	== The Toolbar ==		== The Toolbar ==
	The toolbar provides ~~functions~~ functions to set the outcome of the current step, to add comments and to attach data files or screenshots to the report.		The toolbar provides functions to set the outcome of the current step, to add comments and to attach data files or screenshots to the report.

	Of special ~~relevante~~ are the ~~"Next"~~buttons (triangular right arrows); these confirm the current step and mark it as "''Successful''" (green), "''Failed''" (red) or "''Inconclusive''" (gray).		Of special relevance are the next buttons (triangular right arrows); these confirm the current step and mark it as "''Successful''" (green), "''Failed''" (red) or "''Inconclusive''" (gray).
	The yellow button also stands for "''Success''", but asks for a comment to be added as warning to the final report and log file.		The yellow button also stands for "''Success''", but asks for a comment to be added as warning to the final report and log file.

Matilk: /* Creating and Using own GUI Layouts */ ProgressIndicator

2023-08-28T10:51:43Z

Creating and Using own GUI Layouts: ProgressIndicator

← Nächstältere Version		Version vom 28. August 2023, 10:51 Uhr
Zeile 307:		Zeile 307:
	: If your manual test consists of a large number of test cases, you might want to add a progress indicator to the GUI, to see how much you already accomplished and how many test cases remain to be completed. Of course there are other use cases as well, but this one can be seen in ''MT - TestStep with Expected & TestCase Progress''.		: If your manual test consists of a large number of test cases, you might want to add a progress indicator to the GUI, to see how much you already accomplished and how many test cases remain to be completed. Of course there are other use cases as well, but this one can be seen in ''MT - TestStep with Expected & TestCase Progress''.
	: The ProgressIndicator takes the progress as ''Model''. Optionally you can set ''Total'' (also in the ''Basics'' tab) which will be 100 otherwise. So you can either provide the percentage in the model or the absolute number and additionally the total. In the ''Details'' tab, you can check ''Show As Proportion'', to change the label inside the ProgressIndicator to show amount of total instead of the percentage, or uncheck ''Show Percentage'' to not show a label at all.		: The ProgressIndicator takes the progress as ''Model''. Optionally you can set ''Total'' (also in the ''Basics'' tab) which will be 100 otherwise. So you can either provide the percentage in the model or the absolute number and additionally the total. In the ''Details'' tab, you can check ''Show As Proportion'', to change the label inside the ProgressIndicator to show amount of total instead of the percentage, or uncheck ''Show Percentage'' to not show a label at all.
	: ''MT - TestStep with Expected & TestCase Progress'' uses the predefined aspects ''currentTestCaseIndex'' and ''numberOfTestCases'' for model and total, which are calculated by the block ''TestCaseProgressInfo''.		: ''MT - TestStep with Expected & TestCase Progress'' uses the predefined aspects ''currentTestCaseIndex'' and ''numberOfTestCases'' for model and total, which are calculated by the block ''TestCaseProgressInfo''. This setup only works if used inside a test plan; nested test plans will work as well.
	: You find the ProgressIndicator in the Widget Gallery under ''Misc''. There is also a round variant for a pie chart like representation.		: You find the ProgressIndicator in the Widget Gallery under ''Misc''. There is also a round variant for a pie chart like representation.
	: [[Datei:Manual Test 33.png\|800px\|Example Usage of ProgressIndicator]]		: [[Datei:Manual Test 33.png\|800px\|Example Usage of ProgressIndicator]]

← Nächstältere Version		Version vom 28. August 2023, 13:01 Uhr
Zeile 166:		Zeile 166:
	[[Datei:Manual Test 8.png]]		[[Datei:Manual Test 8.png]]

	=== Manual Test Wizard – Start ===		== Manual Test Wizard – Start ==

	This action opens the wizard with individual values for position, size and behavior.		This action opens the wizard with individual values for position, size and behavior.
Zeile 190:		Zeile 190:
	<br>		<br>

	=== Manual Test Wizard – Preset Values ===		== Manual Test Wizard – Preset Values ==

	You can preset the layout before the wizard is opened the first time with this action.		You can preset the layout before the wizard is opened the first time with this action.
	The meaning of the values is as described in the above “<CODE>Manual Test Wizard – Start</CODE>” action; these will be used when the first manual test step is executed.		The meaning of the values is as described in the above “<CODE>Manual Test Wizard – Start</CODE>” action; these will be used when the first manual test step is executed.

	=== Manual TestStep (API) ===		== Manual TestStep (API) ==

	You'll find a actions for different uses in the library. The 3 most heavily used are described below.		You'll find a actions for different uses in the library. The 3 most heavily used are described below.
Zeile 201:		Zeile 201:
	be reminded, that the presented texts are not required to be defined as constants. They might of course be generated by another step. For example, they could could be read from a database or a file, or be generated dynamically from text fragments.		be reminded, that the presented texts are not required to be defined as constants. They might of course be generated by another step. For example, they could could be read from a database or a file, or be generated dynamically from text fragments.

	==== Manual TestStep (Text) ====		=== Manual TestStep (Text) ===

	This action presents the texts as simple text.		This action presents the texts as simple text.
Zeile 209:		Zeile 209:
	[[Datei:Manual Test 9.png]]		[[Datei:Manual Test 9.png]]

	==== Manual TestStep (HTML) ====		=== Manual TestStep (HTML) ===

	This action presents the text in the wizard as HTML formatted text.		This action presents the text in the wizard as HTML formatted text.
Zeile 221:		Zeile 221:
	[[Datei:Manual Test 10.png]]		[[Datei:Manual Test 10.png]]

	==== Manual TestStep (SimpleWikiStyle) ====		=== Manual TestStep (SimpleWikiStyle) ===

	A text format commonly used in Wikis (so called "Wikistyle") can be used to format simple bullet lists, headlines etc. without a need for HTML. For that, text in Wiki-style can be internally translated to HTML and presented as such.		A text format commonly used in Wikis (so called "Wikistyle") can be used to format simple bullet lists, headlines etc. without a need for HTML. For that, text in Wiki-style can be internally translated to HTML and presented as such.
Zeile 240:		Zeile 240:
	Here as well, the text is presented in the wizard in an HTML viewer.		Here as well, the text is presented in the wizard in an HTML viewer.

	==== Manual TestStep (MarkDown) ====		=== Manual TestStep (MarkDown) ===

	A text format commonly known as MarkDown can be used to create a formatted text format with headlines, bullet and numbered lists, etc. without a need for HTML. For that, text in MarkDown will be internally translated to HTML and presented as such.		A text format commonly known as MarkDown can be used to create a formatted text format with headlines, bullet and numbered lists, etc. without a need for HTML. For that, text in MarkDown will be internally translated to HTML and presented as such.
Zeile 277:		Zeile 277:
	so you can embed plain html for formating.		so you can embed plain html for formating.

	=== Creating and Using own GUI Layouts ===		== Creating and Using own GUI Layouts ==
	If you want to further customize the layout of you test steps, you can also create your own GUI and fill that with your content. In the folder ''Sample Wizard GUIs'' of the ''Manual Test Interface'' you can find several examples that you can use as inspiration or starting point to create your own layout.		If you want to further customize the layout of you test steps, you can also create your own GUI and fill that with your content. In the folder ''Sample Wizard GUIs'' of the ''Manual Test Interface'' you can find several examples that you can use as inspiration or starting point to create your own layout.