Expecco Reflection Library - Versionsgeschichte

Cg: /* Importing the Library */

2026-03-25T17:22:51Z

Importing the Library

← Nächstältere Version		Version vom 25. März 2026, 17:22 Uhr
Zeile 11:		Zeile 11:
	* Navigate to the "Expecco Library" folder (there should be a shortcut navigation item in the dialog; if not, find the library folder under the expecco installation path (typically "<code>programFiles\exept\expecco</code>")		* Navigate to the "Expecco Library" folder (there should be a shortcut navigation item in the dialog; if not, find the library folder under the expecco installation path (typically "<code>programFiles\exept\expecco</code>")
	* select the "<code>Expecco Reflection Library.ets</code>" and click "''OK''"		* select the "<code>Expecco Reflection Library.ets</code>" and click "''OK''"
			* takie a look at the examples found in the "Test/Demo" page of those action blocks; for example the "Expecco: Open" action.

	== Typical Uses ==		== Typical Uses ==

Cg: /* Importing the Library */

2026-03-25T17:20:34Z

Importing the Library

← Nächstältere Version		Version vom 25. März 2026, 17:20 Uhr
Zeile 8:		Zeile 8:

	== Importing the Library ==		== Importing the Library ==
	* In the tree, select the folder named ''Imports'' and select the popup menu function "Import Library".		* In the tree, select the folder named "''Imports''" and select the popup menu function "Import Library".
	* Navigate to the "Expecco Library" folder (there should be a shortcut navigation item in the dialog; if not, find the library folder under the expecco installation path (typically "<code>programFiles\exept\expecco</code>")		* Navigate to the "Expecco Library" folder (there should be a shortcut navigation item in the dialog; if not, find the library folder under the expecco installation path (typically "<code>programFiles\exept\expecco</code>")
	* select the "<code>Expecco Reflection Library.ets</code>" and click "''OK''"		* select the "<code>Expecco Reflection Library.ets</code>" and click "''OK''"

Cg: /* Introduction */

2026-03-25T17:20:17Z

Introduction

← Nächstältere Version		Version vom 25. März 2026, 17:20 Uhr
Zeile 6:		Zeile 6:

	For more information, please refer to the documentation and examples inside the library.		For more information, please refer to the documentation and examples inside the library.

			== Importing the Library ==
			* In the tree, select the folder named ''Imports'' and select the popup menu function "Import Library".
			* Navigate to the "Expecco Library" folder (there should be a shortcut navigation item in the dialog; if not, find the library folder under the expecco installation path (typically "<code>programFiles\exept\expecco</code>")
			* select the "<code>Expecco Reflection Library.ets</code>" and click "''OK''"

	== Typical Uses ==		== Typical Uses ==

Cg: /* Examples */

2023-02-16T10:35:48Z

Examples

← Nächstältere Version		Version vom 16. Februar 2023, 10:35 Uhr
Zeile 82:		Zeile 82:
	<<picture to be added>>		<<picture to be added>>

	All this is wrapped up into one action, which is defined as "to be automatically executed ~~ehen~~ the suite is loaded":		All this is wrapped up into one action, which is defined as "to be automatically executed When the suite is loaded":

	<<picture to be added>>		<<picture to be added>>

Cg: /* Browser Manipulation */

2023-02-16T10:34:21Z

Browser Manipulation

← Nächstältere Version		Version vom 16. Februar 2023, 10:34 Uhr
Zeile 31:		Zeile 31:
	=== Browser Manipulation ===		=== Browser Manipulation ===

	These include blocks to simulate various user actions, either towards the currently running expecco application, or to a secondary expecco window. For example, to open, close expecco windows, to switch to particular tabs,		These include action blocks to simulate various user actions, either towards the currently running expecco application, or to a secondary expecco window. For example, to open, close expecco windows, to switch to particular tabs,
	or to change the selection in the item tree.		or to change the selection in the item tree.

Cg: /* Typical Uses */

2022-03-13T12:34:28Z

Typical Uses

← Nächstältere Version		Version vom 13. März 2022, 12:34 Uhr
Zeile 18:		Zeile 18:
	* conversion/migration of existing test cases		* conversion/migration of existing test cases

	Expecco customers have used this library to:		In the past, Expecco customers have used this library to:
	* fetch test specs from a QM system, generate test plans on-the-fly, and upload results		* fetch test specs from a QM system, generate test plans on-the-fly, and upload results
			* build suites from excel tables (i.e. from a CSV document)
	* fetch test parameters from a custom data base		* fetch test parameters from a custom data base
	* merge multiple partial test suites into a a configurable test-run suite		* merge multiple partial test suites into a a configurable test-run suite

Cg: /* Typical Uses */

2022-03-13T12:31:40Z

Typical Uses

← Nächstältere Version		Version vom 13. März 2022, 12:31 Uhr
Zeile 17:		Zeile 17:
	* generation of custom documents from suites		* generation of custom documents from suites
	* conversion/migration of existing test cases		* conversion/migration of existing test cases

			Expecco customers have used this library to:
			* fetch test specs from a QM system, generate test plans on-the-fly, and upload results
			* fetch test parameters from a custom data base
			* merge multiple partial test suites into a a configurable test-run suite
			* automatic adding of procedures to a suite
			* automatic extraction of documentation from a suite into custom formats
			* automatic generation of test steps to call python or C functions, given header files or annotated doxygen source files.

	== Functionality ==		== Functionality ==

Cg: /* Typical Uses */

2022-03-13T12:28:02Z

Typical Uses

← Nächstältere Version		Version vom 13. März 2022, 12:28 Uhr
Zeile 10:		Zeile 10:

	The reflection library can be used to:		The reflection library can be used to:
	* automatically generate ~~testsuites~~ from textual descriptions		* automatically generate test suites from textual descriptions or DB query results
	* automatically generate datatypes (e.g. from ~~textual~~ descriptions)		* automatically generate datatypes (e.g. from descriptions, header files etc.)
	* merge, filter ~~testsuites~~		* merge, filter and execute test suites
	* bulk renaming, bulk annotating of elements in a number of suites		* bulk renaming, bulk annotating of elements in a number of suites
	* extraction of annotations from a number of suites		* extraction of annotations from a number of suites
	* generation of custom documents from suites		* generation of custom documents from suites
	* conversion/migration of existing ~~testcases~~		* conversion/migration of existing test cases

	== Functionality ==		== Functionality ==

Cg: /* Introduction */

2022-03-13T12:26:40Z

Introduction

← Nächstältere Version		Version vom 13. März 2022, 12:26 Uhr
Zeile 1:		Zeile 1:
	== Introduction ==		== Introduction ==
	The Reflection Library contains building blocks to automate expecco itself and to construct ~~test~~ ~~suits~~ ~~automatically~~.		The Reflection Library contains building blocks to automate expecco itself and to construct or modify a project tree.

	Its main use is to automatically generate test suites or libraries.		Its main use is to automatically generate test suites or libraries.
	For example, to import specifications in a textual format, a database or a QM-system and generate test skeletons or concrete action blocks and/or test suites.		<br>For example, to import specifications in a textual format, a database or a QM-system and generate test skeletons or concrete action blocks and/or test suites.

	For more information, please refer to the documentation and examples		For more information, please refer to the documentation and examples inside the library.
	inside the library.

	== Typical Uses ==		== Typical Uses ==

Cg: /* Examples */

2021-09-14T10:19:40Z

Examples

← Nächstältere Version		Version vom 14. September 2021, 10:19 Uhr
Zeile 56:		Zeile 56:
	Assuming that the database contains a table named "TestSpecs", which relates tests with parameters and test steps.		Assuming that the database contains a table named "TestSpecs", which relates tests with parameters and test steps.
	The following asks the operator for a test-name, queries the database and collects steps and parameters:		The following asks the operator for a test-name, queries the database and collects steps and parameters:

	<<picture to be added>>		<<picture to be added>>

	Then that information is passed to a test generator, which		Then that information is passed to a test generator, which
	* creates a testplan,		* creates a testplan,
	* enumerates the steps and adds test cases,		* enumerates the steps and adds test cases,
	* enumerates the parameters and creates variables		* enumerates the parameters and creates variables

	<<picture to be added>>		<<picture to be added>>

	Finally,		Finally,
	* the test is executed,		* the test is executed,
	* a report generated,		* a report generated,
	* and also written back to the database		* and also written back to the database

	<<picture to be added>>		<<picture to be added>>

	All this is wrapped up into one action, which is defined as "to be automatically executed ehen the suite is loaded":		All this is wrapped up into one action, which is defined as "to be automatically executed ehen the suite is loaded":

	<<picture to be added>>		<<picture to be added>>