Folder Element/en - Versionsgeschichte

Cg: /* Define Useful Actions as Menu Functions */

2026-03-08T00:14:14Z

Define Useful Actions as Menu Functions

← Nächstältere Version		Version vom 8. März 2026, 00:14 Uhr
Zeile 20:		Zeile 20:
	=== Define Useful Actions as Menu Functions ===		=== Define Useful Actions as Menu Functions ===

	Add a folder named "menu Actions" or similar, place ~~and~~ useful actions for test setup, equipment startup and shutdown or calibration into it. When this folder is defined as the project's operation menu folder (in the test suite's "Misc" ~~editor page~~), you can quickly execute those functions via the main menu. ~~For~~ ~~more~~ ~~information,~~ ~~see~~ ~~[[User~~ ~~Defined~~ ~~Menu~~ ~~Items]]~~.		Add a folder named "menu Actions" or similar and place useful actions for test setup, equipment startup and shutdown or calibration into it. When this folder is defined as the project's operation menu folder (in the test suite's "''Misc''" tab), you can quickly execute those functions via the main menu. You can also import such menu actions from imported libraries.

			For more information, see [[User Defined Menu Items]].

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

Cg: /* Demos and Examples */

2026-03-08T00:12:30Z

Demos and Examples

← Nächstältere Version		Version vom 8. März 2026, 00:12 Uhr
Zeile 16:		Zeile 16:
	Add a folder named "Playground", "Sandbox" or "Examples" or similar and place compound action blocks which demonstrate key features or low level access functionality. Other team members may later easily find those and play with the examples. It is also a good idea to place simple connection, communication, [[Glossary/en#SUT_.28System_Under_Test.29\|SUT]] is running tests, setup and shutdown blocks there (unless those are commonly used, then put them into API/Exported).		Add a folder named "Playground", "Sandbox" or "Examples" or similar and place compound action blocks which demonstrate key features or low level access functionality. Other team members may later easily find those and play with the examples. It is also a good idea to place simple connection, communication, [[Glossary/en#SUT_.28System_Under_Test.29\|SUT]] is running tests, setup and shutdown blocks there (unless those are commonly used, then put them into API/Exported).

	Add little demo setups for individual ~~actions~~ into the "Demo" tab. Beside providing unit-tests for your actions, they are often better as documentation than textual descriptions. They are also useful as copy-paste sources for users of the action.		Add little demo setups for individual into the action's "Demo" tab. Beside providing unit-tests for your actions, they are often better as documentation than textual descriptions. They are also useful as copy-paste sources for users of the action.

	=== Define Useful Actions as Menu Functions ===		=== Define Useful Actions as Menu Functions ===

Cg: /* Demos and Examples */

2026-03-08T00:11:51Z

Demos and Examples

← Nächstältere Version		Version vom 8. März 2026, 00:11 Uhr
Zeile 15:		Zeile 15:

	Add a folder named "Playground", "Sandbox" or "Examples" or similar and place compound action blocks which demonstrate key features or low level access functionality. Other team members may later easily find those and play with the examples. It is also a good idea to place simple connection, communication, [[Glossary/en#SUT_.28System_Under_Test.29\|SUT]] is running tests, setup and shutdown blocks there (unless those are commonly used, then put them into API/Exported).		Add a folder named "Playground", "Sandbox" or "Examples" or similar and place compound action blocks which demonstrate key features or low level access functionality. Other team members may later easily find those and play with the examples. It is also a good idea to place simple connection, communication, [[Glossary/en#SUT_.28System_Under_Test.29\|SUT]] is running tests, setup and shutdown blocks there (unless those are commonly used, then put them into API/Exported).

			Add little demo setups for individual actions into the "Demo" tab. Beside providing unit-tests for your actions, they are often better as documentation than textual descriptions. They are also useful as copy-paste sources for users of the action.

	=== Define Useful Actions as Menu Functions ===		=== Define Useful Actions as Menu Functions ===

Cg: /* Introduction */

2026-03-08T00:08:16Z

Introduction

← Nächstältere Version		Version vom 8. März 2026, 00:08 Uhr
Zeile 2:		Zeile 2:
	Folder elements are used to group related items. Notice that any action block item can have sub items. Besides being used to specify user-defined action menus (see [[Testsuite Editor-Metadata Editor/en \| Testsuite Editor]]), folders have no special semantic relevance.		Folder elements are used to group related items. Notice that any action block item can have sub items. Besides being used to specify user-defined action menus (see [[Testsuite Editor-Metadata Editor/en \| Testsuite Editor]]), folders have no special semantic relevance.

	[[Datei:bulb.png\|20px]]Notice that in contrast to other test tools, folders are NOT used to group testcases into test sequences or sub-activities into a composite ~~activities~~. They are only used for organization - not to specify any execution order or execution behavior.		[[Datei:bulb.png\|20px]]Notice that in contrast to other test tools, folders are NOT used to group testcases into test sequences or sub-activities into a composite activity. They are only used for organization - not to specify any execution order or execution behavior.

	Folder elements only provide a single editor tab, into which documentation related to the folder can be entered. If this documentation is left empty, the documentation editor presents a short summary of the containing element's documentation texts (read-only).		Folder elements only provide a single editor tab, into which documentation related to the folder can be entered. If this documentation is left empty, the documentation editor presents a short summary of the containing element's documentation texts (read-only).

Sv: Änderung übernommen aus altem Wiki von cg, 19.11.25

2026-02-23T12:48:51Z

Änderung übernommen aus altem Wiki von cg, 19.11.25

← Nächstältere Version		Version vom 23. Februar 2026, 12:48 Uhr
Zeile 2:		Zeile 2:
	Folder elements are used to group related items. Notice that any action block item can have sub items. Besides being used to specify user-defined action menus (see [[Testsuite Editor-Metadata Editor/en \| Testsuite Editor]]), folders have no special semantic relevance.		Folder elements are used to group related items. Notice that any action block item can have sub items. Besides being used to specify user-defined action menus (see [[Testsuite Editor-Metadata Editor/en \| Testsuite Editor]]), folders have no special semantic relevance.

	[[Datei:~~point_right~~.png\|20px]] Notice that in contrast to other test tools, folders are NOT used to group testcases into test sequences or sub-activities into a composite activities. They are only used for organization - not to specify any execution order or execution behavior.		[[Datei:bulb.png\|20px]]Notice that in contrast to other test tools, folders are NOT used to group testcases into test sequences or sub-activities into a composite activities. They are only used for organization - not to specify any execution order or execution behavior.

	Folder elements only provide a single editor tab, into which documentation related to the folder can be entered. If this documentation is left empty, the documentation editor presents a short summary of the containing element's documentation texts (read-only).		Folder elements only provide a single editor tab, into which documentation related to the folder can be entered. If this documentation is left empty, the documentation editor presents a short summary of the containing element's documentation texts (read-only).

Cg: /* See Also */

2025-02-04T10:04:58Z

Cg am 4. Februar 2025 um 10:02 Uhr

2025-02-04T10:02:31Z

← Nächstältere Version		Version vom 4. Februar 2025, 10:02 Uhr
Zeile 19:		Zeile 19:

	Add a folder named "menu Actions" or similar, place and useful actions for test setup, equipment startup and shutdown or calibration into it. When this folder is defined as the project's operation menu folder (in the test suite's "Misc" editor page), you can quickly execute those functions via the main menu. For more information, see [[User Defined Menu Items]].		Add a folder named "menu Actions" or similar, place and useful actions for test setup, equipment startup and shutdown or calibration into it. When this folder is defined as the project's operation menu folder (in the test suite's "Misc" editor page), you can quickly execute those functions via the main menu. For more information, see [[User Defined Menu Items]].

			== See Also ==

			[[Tree Elements]]

	[[Category: Tree Elements]]		[[Category: Tree Elements]]

Cg am 10. November 2022 um 14:15 Uhr

2022-11-10T14:15:00Z

← Nächstältere Version		Version vom 10. November 2022, 14:15 Uhr
Zeile 14:		Zeile 14:
	=== Demos and Examples ===		=== Demos and Examples ===

	Add a folder named "Playground", "Sandbox" or "Examples" or similar and place compound action blocks which demonstrate key features or low level access functionality. Other team members may later easily find those and play with the examples. It is also a good idea to place simple connection, communication, SUT is running tests, setup and shutdown blocks there (unless those are commonly used, then put them into API/Exported).		Add a folder named "Playground", "Sandbox" or "Examples" or similar and place compound action blocks which demonstrate key features or low level access functionality. Other team members may later easily find those and play with the examples. It is also a good idea to place simple connection, communication, [[Glossary/en#SUT_.28System_Under_Test.29\|SUT]] is running tests, setup and shutdown blocks there (unless those are commonly used, then put them into API/Exported).

	=== Define Useful Actions as Menu Functions ===		=== Define Useful Actions as Menu Functions ===

Cg: /* Introduction */

2019-12-20T15:41:43Z

Introduction

← Nächstältere Version		Version vom 20. Dezember 2019, 15:41 Uhr
Zeile 2:		Zeile 2:
	Folder elements are used to group related items. Notice that any action block item can have sub items. Besides being used to specify user-defined action menus (see [[Testsuite Editor-Metadata Editor/en \| Testsuite Editor]]), folders have no special semantic relevance.		Folder elements are used to group related items. Notice that any action block item can have sub items. Besides being used to specify user-defined action menus (see [[Testsuite Editor-Metadata Editor/en \| Testsuite Editor]]), folders have no special semantic relevance.

	Notice that in contrast to other test tools, folders are NOT used to group testcases into test sequences or sub-activities into a composite activities. They are only used for organization - not to specify any execution order or execution behavior.		[[Datei:point_right.png\|20px]] Notice that in contrast to other test tools, folders are NOT used to group testcases into test sequences or sub-activities into a composite activities. They are only used for organization - not to specify any execution order or execution behavior.

	Folder elements only provide a single editor tab, into which documentation related to the folder can be entered. If this documentation is left empty, the documentation editor presents a short summary of the containing element's documentation texts (read-only).		Folder elements only provide a single editor tab, into which documentation related to the folder can be entered. If this documentation is left empty, the documentation editor presents a short summary of the containing element's documentation texts (read-only).

Cg: /* Public vs. Private Actions */

2019-09-05T10:10:03Z

Public vs. Private Actions

← Nächstältere Version		Version vom 5. September 2019, 10:10 Uhr
Zeile 10:		Zeile 10:
	=== Public vs. Private Actions ===		=== Public vs. Private Actions ===

	In imported library suites, put stuff which is supposed to be used by importing projects into a separate folder named "API" or "Exported". This makes it easier for other team members to find reusable stuff. You may also want to change the folder's icon color (~~popupMenu~~ -> "Misc" -> "IconColor") to emphasize particular folders (such as "red" for obsolete or experimental actions, "green" for released/public actions etc.)		In imported library suites, put stuff which is supposed to be used by importing projects into a separate folder named "API" or "Exported". This makes it easier for other team members to find reusable stuff. You may also want to change the folder's icon color (contextMenu → "''Misc''" → "''IconColor''") to emphasize particular folders (such as "red" for obsolete or experimental actions, "green" for released/public actions etc.)

	=== Demos and Examples ===		=== Demos and Examples ===

← Nächstältere Version		Version vom 4. Februar 2025, 10:04 Uhr
Zeile 23:		Zeile 23:

	[[Tree Elements]]		[[Tree Elements]]
			<br>[[ Navigation Tree ]]

	[[Category: Tree Elements]]		[[Category: Tree Elements]]