ManualTest/en - Versionsgeschichte

Matilk: /* Example Session */ link to tutorial page

2023-08-21T15:32:55Z

Example Session: link to tutorial page

← Nächstältere Version		Version vom 21. August 2023, 15:32 Uhr
Zeile 31:		Zeile 31:

	= Example Session =		= Example Session =
	Please take a look at the tutorial or execute one of the examples in the manual test library.		Please take a look at the [[Manual_Test_Tutorial/en\|tutorial]] or execute one of the examples in the manual test library.

	= Importing Manual Tests from Existing Specs =		= Importing Manual Tests from Existing Specs =

Matilk: headline levels; defining manual steps

2023-08-21T15:31:41Z

headline levels; defining manual steps

Cg: /* Writing your own Importer */

2023-06-21T10:18:26Z

Writing your own Importer

← Nächstältere Version		Version vom 21. Juni 2023, 10:18 Uhr
Zeile 54:		Zeile 54:

	==== Writing your own Importer ====		==== Writing your own Importer ====
	By use of the [[Expecco_Reflection_Library\|Expecco Reflection Library]], possibly combined with XML imports, custom importers for arbitrary formats or from databases are possible. Please look into the reflection library for examples, or plan for an online teaching session.		By use of the [[Expecco_Reflection_Library\|Expecco Reflection Library]], possibly combined with [[XML_Parser_and_DOM_Tree_Library\|XML imports]], custom importers for arbitrary formats or from databases are possible. Please look into the reflection library for examples, or plan for an online teaching session.

	=== Running Manual Tests ===		=== Running Manual Tests ===

Cg: /* Writing your own Importer */

2023-06-21T10:17:40Z

Writing your own Importer

← Nächstältere Version		Version vom 21. Juni 2023, 10:17 Uhr
Zeile 54:		Zeile 54:

	==== Writing your own Importer ====		==== Writing your own Importer ====
	By use of the Expecco Reflection Library, possibly combined with XML imports, custom importers for arbitrary formats or from databases are possible. Please look into the reflection library for examples, or plan for an online teaching session.		By use of the [[Expecco_Reflection_Library\|Expecco Reflection Library]], possibly combined with XML imports, custom importers for arbitrary formats or from databases are possible. Please look into the reflection library for examples, or plan for an online teaching session.

	=== Running Manual Tests ===		=== Running Manual Tests ===

Cg: /* Interacting with the Manual Test Wizard */

2023-06-21T10:17:01Z

Interacting with the Manual Test Wizard

← Nächstältere Version		Version vom 21. Juni 2023, 10:17 Uhr
Zeile 66:		Zeile 66:
	See the tutorial for detailed instructions.		See the tutorial for detailed instructions.

	If the remote control service is enabled, the wizard is mirrored on remote UIs. User interactions are also possible via a Webbrowser, Android- or IOS-device.		If the remote control service is enabled, the wizard is mirrored on remote UIs. User interactions are then also possible via a Webbrowser, Android- or IOS-device.

	=== Hints & Tips ===		=== Hints & Tips ===

Cg: /* Running Manual Tests */

2023-06-21T10:16:45Z

Running Manual Tests

← Nächstältere Version		Version vom 21. Juni 2023, 10:16 Uhr
Zeile 61:		Zeile 61:
	However, whenever a manual test step is executed, the Manual Test Wizard pops up and asks the user for confirmation. You can mix and match manual test steps with any other regular action steps in any diagram or test plan.		However, whenever a manual test step is executed, the Manual Test Wizard pops up and asks the user for confirmation. You can mix and match manual test steps with any other regular action steps in any diagram or test plan.

	~~You~~ ~~may~~ ~~also~~ later replace manual test actions with fully automated test actions.		If desired, you may later (incrementally) replace manual test actions with fully automated test actions.

⚫	If the remote control service is enabled, the wizard is mirrored on remote UIs. User interactions are also possible via a Webbrowser, Android- or IOS-device.

	==== Interacting with the Manual Test Wizard ====		==== Interacting with the Manual Test Wizard ====
	See the tutorial for detailed instructions.		See the tutorial for detailed instructions.

		⚫	If the remote control service is enabled, the wizard is mirrored on remote UIs. User interactions are also possible via a Webbrowser, Android- or IOS-device.

	=== Hints & Tips ===		=== Hints & Tips ===

Cg: /* Running Manual Tests */

2023-06-21T10:15:59Z

Running Manual Tests

← Nächstältere Version		Version vom 21. Juni 2023, 10:15 Uhr
Zeile 63:		Zeile 63:
	You may also later replace manual test actions with fully automated test actions.		You may also later replace manual test actions with fully automated test actions.

	If the remote control service is enabled, ~~user~~ interactions are also possible via a Webbrowser, Android- or IOS-device.		If the remote control service is enabled, the wizard is mirrored on remote UIs. User interactions are also possible via a Webbrowser, Android- or IOS-device.

	==== Interacting with the Manual Test Wizard ====		==== Interacting with the Manual Test Wizard ====

Cg: /* Running Manual Tests */

2023-06-21T10:15:22Z

Running Manual Tests

← Nächstältere Version		Version vom 21. Juni 2023, 10:15 Uhr
Zeile 62:		Zeile 62:

	You may also later replace manual test actions with fully automated test actions.		You may also later replace manual test actions with fully automated test actions.

			If the remote control service is enabled, user interactions are also possible via a Webbrowser, Android- or IOS-device.

	==== Interacting with the Manual Test Wizard ====		==== Interacting with the Manual Test Wizard ====

Cg: /* Importing Manual Tests from Existing Specs */

2023-06-21T10:13:50Z

Importing Manual Tests from Existing Specs

← Nächstältere Version		Version vom 21. Juni 2023, 10:13 Uhr
Zeile 52:		Zeile 52:
	==== Importing Specs from JIRA or AQUA ====		==== Importing Specs from JIRA or AQUA ====
	Please refer to the Jira or Aqua plugin documentation.		Please refer to the Jira or Aqua plugin documentation.

			==== Writing your own Importer ====
			By use of the Expecco Reflection Library, possibly combined with XML imports, custom importers for arbitrary formats or from databases are possible. Please look into the reflection library for examples, or plan for an online teaching session.

	=== Running Manual Tests ===		=== Running Manual Tests ===

Cg: /* Importing Specs from Word- or Excel Documents */

2023-06-21T10:11:34Z

Importing Specs from Word- or Excel Documents

← Nächstältere Version		Version vom 21. Juni 2023, 10:11 Uhr
Zeile 47:		Zeile 47:

	A similar regular scheme can be defined when importing a Word or OpenOffice document; here paragraph levels define where test cases or test steps start.		A similar regular scheme can be defined when importing a Word or OpenOffice document; here paragraph levels define where test cases or test steps start.

			The importer can be customized within a reasonable range. For example, column numbers and/or headers which define test cases and test steps, sheet numbers (in excel) and others are configurable.

	==== Importing Specs from JIRA or AQUA ====		==== Importing Specs from JIRA or AQUA ====

← Nächstältere Version		Version vom 21. August 2023, 15:31 Uhr
Zeile 1:		Zeile 1:
	=== Introduction ===		= Introduction =

	Manual test steps are inserted into a test case or test plan for activities which cannot be automated or for which automation is not possible due to cost, complexity or general verifiability. They can also be used during a transition period, while converting from manual testing via partial automatic testing to full automatic testing.		Manual test steps are inserted into a test case or test plan for activities which cannot be automated or for which automation is not possible due to cost, complexity or general verifiability. They can also be used during a transition period, while converting from manual testing via partial automatic testing to full automatic testing.
Zeile 9:		Zeile 9:
	the answers are either logged or generated at output pins and compared against expected values.		the answers are either logged or generated at output pins and compared against expected values.

	=== Defining Manual Tests by Placing Steps (Programatic Definition) ===		= Defining Manual Tests by Placing Steps (Programatic Definition) =

	Create a new compound action and place manual test steps into it. There are also now quick menu functions in the project tree, to generate the most often needed manual step actions (found in the "Manual Test" item under the "tests" quick menu).		Create a new compound action and place manual test steps into it. There are also now quick menu functions in the project tree, to generate the most often needed manual step actions (found in the "Manual Test" item under the "tests" quick menu).
Zeile 17:		Zeile 17:
	Notice that the diagram editor has a special entry for manual test steps in its context menu.		Notice that the diagram editor has a special entry for manual test steps in its context menu.

	==== Predefined Blocks for Manual Test Steps ====		== Predefined Blocks for Manual Test Steps ==
		⚫	You'll find a number of predefined manual test actions in the library in ''Manual Test Steps (API)'' or ''Manual Test Step Templates''. Also, the treeview's toolbar offers quick menu entries to create the most common.

			These blocks use an already defined GUI that you can fill with your content that you can specify by a text at the input pin. You can choose between different formats for the text, like plain text, HTML or a wiki style.
⚫	You'll find a number of predefined manual test actions in the library. Also, the treeview's toolbar offers quick menu entries to create the most common.

	==== Defining your own GUI in a Manual Test Step ====		== Defining your own GUI in a Manual Test Step ==
	It is possible to define additional custom manual test steps, which can define completely different user interfaces. This is useful, if you want to present additional information (measurement values, screen shots, camera pictures etc.) in the manual test wizard.		It is possible to define additional custom manual test steps, which can define completely different user interfaces. This is useful, if you want to present additional information (measurement values, screen shots, camera pictures etc.) in the manual test wizard.
	Or, if you want to ask the operator for multiple values (and have multiple input fields, possibly with value-plausibility checks) in the UI.		Or, if you want to ask the operator for multiple values (and have multiple input fields, possibly with value-plausibility checks) in the UI.
Zeile 27:		Zeile 28:
	A few examples are found in the library; especially one which presents an image (as when you want to show a schematic of where to place a probe or where to read a measurement value).		A few examples are found in the library; especially one which presents an image (as when you want to show a schematic of where to place a probe or where to read a measurement value).

			Take a look at the blocks in ''Sample Wizard GUIs''. These blocks are using the basic block ''MT - GUI TestStep+'', which takes a [[GUIBlock_Element/en\|GUI block]] at its first pin. Additionally you can set some parameters and specify a number of fixed aspect as well as an unlimited number of custom aspects (the variable pins at the end). These aspects then can be used in the aspects section of a component, to display the information you passed in the GUI. You can use the aspects in the same way to get return values from the test step. The output pin ''infoValues'' will return a Dictionary with all aspect names and their values after the test.
⚫	=== Example Session ===

		⚫	= Example Session =
	Please take a look at the tutorial or execute one of the examples in the manual test library.		Please take a look at the tutorial or execute one of the examples in the manual test library.

	=== Importing Manual Tests from Existing Specs ===		= Importing Manual Tests from Existing Specs =
	Expecco includes an importer for manual test specifications written as Microsoft Word, OpenOffice or Excel document. There are also plugins to import from JIRA and AQUA test management systems. The import features are part of the "Manual Test Import" plugin, which has to be licensed separately.		Expecco includes an importer for manual test specifications written as Microsoft Word, OpenOffice or Excel document. There are also plugins to import from JIRA and AQUA test management systems. The import features are part of the "Manual Test Import" plugin, which has to be licensed separately.

	==== Importing Specs from Word- or Excel Documents ====		== Importing Specs from Word- or Excel Documents ==

	Although certain parameters can be configured for the import format,		Although certain parameters can be configured for the import format,
	the document has to conform to some broad layout, in order for the importer to recognize test steps, subactions, info texts etc.		the document has to conform to some broad layout, in order for the importer to recognize test steps, subactions, info texts etc.
Zeile 50:		Zeile 52:
	The importer can be customized within a reasonable range. For example, column numbers and/or headers which define test cases and test steps, sheet numbers (in excel) and others are configurable.		The importer can be customized within a reasonable range. For example, column numbers and/or headers which define test cases and test steps, sheet numbers (in excel) and others are configurable.

	==== Importing Specs from JIRA or AQUA ====		== Importing Specs from JIRA or AQUA ==
	Please refer to the Jira or Aqua plugin documentation.		Please refer to the Jira or Aqua plugin documentation.

	==== Writing your own Importer ====		== Writing your own Importer ==
	By use of the [[Expecco_Reflection_Library\|Expecco Reflection Library]], possibly combined with [[XML_Parser_and_DOM_Tree_Library\|XML imports]], custom importers for arbitrary formats or from databases are possible. Please look into the reflection library for examples, or plan for an online teaching session.		By use of the [[Expecco_Reflection_Library\|Expecco Reflection Library]], possibly combined with [[XML_Parser_and_DOM_Tree_Library\|XML imports]], custom importers for arbitrary formats or from databases are possible. Please look into the reflection library for examples, or plan for an online teaching session.

	=== Running Manual Tests ===		= Running Manual Tests =

	Manual tests are executed the same way as regular automated tests.		Manual tests are executed the same way as regular automated tests.
Zeile 63:		Zeile 65:
	If desired, you may later (incrementally) replace manual test actions with fully automated test actions.		If desired, you may later (incrementally) replace manual test actions with fully automated test actions.

	==== Interacting with the Manual Test Wizard ====		== Interacting with the Manual Test Wizard ==
	See the tutorial for detailed instructions.		See the tutorial for detailed instructions.

	If the remote control service is enabled, the wizard is mirrored on remote UIs. User interactions are then also possible via a Webbrowser, Android- or IOS-device.		If the remote control service is enabled, the wizard is mirrored on remote UIs. User interactions are then also possible via a Webbrowser, Android- or IOS-device.

	=== Hints & Tips ===		= Hints & Tips =

	=== See Also ===		= See Also =

	[[Manual Test Tutorial/en \| Manual Test Tutorial]]		[[Manual Test Tutorial/en \| Manual Test Tutorial]]