BlockSkill Editor/en - Versionsgeschichte

Mawalch am 4. Januar 2018 um 19:24 Uhr

2018-01-04T19:24:02Z

← Nächstältere Version		Version vom 4. Januar 2018, 19:24 Uhr
Zeile 8:		Zeile 8:
	100V with an error of not more than 5%.		100V with an error of not more than 5%.

	[[Datei:blockRequirement1.~~jpg~~\|800px]]		[[Datei:blockRequirement1.png\|800px]]

	when executed, the built-in resource manager will allocate such a device from the inventory or wait until one becomes available. An error is reported if no such resources exists at all (i.e. if the resource manager would wait "forever").		when executed, the built-in resource manager will allocate such a device from the inventory or wait until one becomes available. An error is reported if no such resources exists at all (i.e. if the resource manager would wait "forever").

Mawalch: expeccoNET -> expecco ALM

2017-06-11T17:04:42Z

expeccoNET -> expecco ALM

← Nächstältere Version		Version vom 11. Juni 2017, 17:04 Uhr
Zeile 15:		Zeile 15:
	This gives expecco the flexibility to dynamically choose among a set of available resources, and decide at execution time, which device or operator is chosen.		This gives expecco the flexibility to dynamically choose among a set of available resources, and decide at execution time, which device or operator is chosen.

	Notice: the resource management works both in a standalone expecco execution environment and when expecco is used with a centralized ~~expeccoNET~~ ~~test~~ a management in operation:		Notice: the resource management works both in a standalone expecco execution environment and when expecco is used with a centralized expecco ALM test management in operation:

	* In standalone mode, the resources are allocated from a given inventory, which is part of the test suite. Multiple such inventories can be defined inside a suite, and one of them ~~choosen~~ in the test's configuration editor.		* In standalone mode, the resources are allocated from a given inventory, which is part of the test suite. Multiple such inventories can be defined inside a suite, and one of them chosen in the test's configuration editor.

	* If executed under control of a central ~~expeccoNET~~ management, this will deal with resource allocation and ensure that resources are correctly managed among all the installed expecco test-execution engines (i.e. among all expecco slaves ~~which~~ are available in the test-host farm).		* If executed under control of a central expecco ALM management, this will deal with resource allocation and ensure that resources are correctly managed among all the installed expecco test-execution engines (i.e. among all expecco slaves that are available in the test-host farm).
	In this case, the inventories as defined within the suite are ignored and ~~expeccoNET~~ will allocate the resources and provide a dynamically constructed inventory to the expecco slave.		In this case, the inventories as defined within the suite are ignored and expecco ALM will allocate the resources and provide a dynamically constructed inventory to the expecco slave.

	[[Category: Editors]]		[[Category: Editors]]

Cg am 18. Oktober 2014 um 12:02 Uhr

2014-10-18T12:02:06Z

← Nächstältere Version		Version vom 18. Oktober 2014, 12:02 Uhr
Zeile 14:		Zeile 14:
	The set of required resources which the action requires for its operation is defined in this editor. This set is not described by an explicit list of required resources, but instead by a list of skills which the allocated resource(s) must have.		The set of required resources which the action requires for its operation is defined in this editor. This set is not described by an explicit list of required resources, but instead by a list of skills which the allocated resource(s) must have.
	This gives expecco the flexibility to dynamically choose among a set of available resources, and decide at execution time, which device or operator is chosen.		This gives expecco the flexibility to dynamically choose among a set of available resources, and decide at execution time, which device or operator is chosen.

			Notice: the resource management works both in a standalone expecco execution environment and when expecco is used with a centralized expeccoNET test a management in operation:

			* In standalone mode, the resources are allocated from a given inventory, which is part of the test suite. Multiple such inventories can be defined inside a suite, and one of them choosen in the test's configuration editor.

			* If executed under control of a central expeccoNET management, this will deal with resource allocation and ensure that resources are correctly managed among all the installed expecco test-execution engines (i.e. among all expecco slaves which are available in the test-host farm).
			In this case, the inventories as defined within the suite are ignored and expeccoNET will allocate the resources and provide a dynamically constructed inventory to the expecco slave.

	[[Category: Editors]]		[[Category: Editors]]

Cg am 18. Oktober 2014 um 11:53 Uhr

2014-10-18T11:53:36Z

← Nächstältere Version		Version vom 18. Oktober 2014, 11:53 Uhr
Zeile 1:		Zeile 1:
	Define resource requirements for the edited block here. These are described by listing the required skills that a resource must have, in order to be useful for the block. The actual resource choice, allocation, reservation and freeing is done at execution time, by the built-in resource manager. The resource manager will fetch an appropriate resource-element from the inventory as present at execution time, reserve it, and allocate for use in the block for the time of the ~~blocks~~ execution. Other blocks which ask for a similar skill will either get another resource (if available), or have to wait until that resource is released.		Define resource requirements for the edited block here. These are described by listing the required skills that a resource must have, in order to be useful for the block. The actual resource choice, allocation, reservation and freeing is done at execution time, by the built-in resource manager. The resource manager will fetch an appropriate resource-element from the inventory as present at execution time, reserve it, and allocate for use in the block for the time of the block's execution. Other blocks which ask for a similar skill will either get another resource (if available), or have to wait until that resource is released.

	Of course, direct resource allocation by name or id is a subset of the above ~~described~~ general mechanism: simply define a numeric or symbolic ID-skill (such as deviceName or deviceID), and specify the skill-requirement to be "deviceName equal someConstant" or "deviceID equal someConstant".		Of course, direct resource allocation by name or id is a subset of the above general mechanism: simply define a numeric or symbolic ID-skill (such as deviceName or deviceID), and specify the skill-requirement to be "deviceName equal someConstant" or "deviceID equal someConstant".

	Also, virtual resources (such as database locks or other synchronization means) can be defined in such a way.		Also, virtual resources (such as database locks or other synchronization means) can be defined in such a way.
Zeile 10:		Zeile 10:
	[[Datei:blockRequirement1.jpg\|800px]]		[[Datei:blockRequirement1.jpg\|800px]]

	when executed, the built-in resource manager will allocate such a device from the inventory.		when executed, the built-in resource manager will allocate such a device from the inventory or wait until one becomes available. An error is reported if no such resources exists at all (i.e. if the resource manager would wait "forever").

	The set of required resources which the action requires for its operation is defined in this editor. This set is not described by an explicit list of required resources, but instead by a list of skills which the allocated resource(s) must have.		The set of required resources which the action requires for its operation is defined in this editor. This set is not described by an explicit list of required resources, but instead by a list of skills which the allocated resource(s) must have.

Sv am 7. April 2014 um 16:51 Uhr

2014-04-07T16:51:18Z

← Nächstältere Version		Version vom 7. April 2014, 16:51 Uhr
Zeile 14:		Zeile 14:
	The set of required resources which the action requires for its operation is defined in this editor. This set is not described by an explicit list of required resources, but instead by a list of skills which the allocated resource(s) must have.		The set of required resources which the action requires for its operation is defined in this editor. This set is not described by an explicit list of required resources, but instead by a list of skills which the allocated resource(s) must have.
	This gives expecco the flexibility to dynamically choose among a set of available resources, and decide at execution time, which device or operator is chosen.		This gives expecco the flexibility to dynamically choose among a set of available resources, and decide at execution time, which device or operator is chosen.

			[[Category: Editors]]

Sv: Sv verschob die Seite BlockSkillEditor/en nach BlockSkill Editor/en, ohne dabei eine Weiterleitung anzulegen

2014-04-04T10:44:50Z

Sv verschob die Seite BlockSkillEditor/en nach BlockSkill Editor/en, ohne dabei eine Weiterleitung anzulegen

← Nächstältere Version	Version vom 4. April 2014, 10:44 Uhr
(kein Unterschied)

Ab am 3. April 2014 um 10:31 Uhr

2014-04-03T10:31:01Z

← Nächstältere Version		Version vom 3. April 2014, 10:31 Uhr
Zeile 1:		Zeile 1:
	Define resource requirements for the edited block here. ~~Thesse~~ are described by listing the required skills that a resource must have, in order to be useful for the block. The actual resource choice, allocation, reservation and freeing is done at execution time, by the built-in resource manager. The resource manager will fetch an appropriate resource-element from the inventory as present at execution time, reserve it, and allocate for use in the block for the time of the blocks execution. Other blocks which ask for a similar skill will either get another resource (if ~~avaliable~~), or have to wait until that resource is released.		Define resource requirements for the edited block here. These are described by listing the required skills that a resource must have, in order to be useful for the block. The actual resource choice, allocation, reservation and freeing is done at execution time, by the built-in resource manager. The resource manager will fetch an appropriate resource-element from the inventory as present at execution time, reserve it, and allocate for use in the block for the time of the blocks execution. Other blocks which ask for a similar skill will either get another resource (if available), or have to wait until that resource is released.

	Of course, direct resource allocation by name or id is a subset of the above described general mechanism: simply define a numeric or symbolic ID-skill (such as deviceName or deviceID), and specify the skill-requirement to be "deviceName equal someConstant" or "deviceID equal someConstant".		Of course, direct resource allocation by name or id is a subset of the above described general mechanism: simply define a numeric or symbolic ID-skill (such as deviceName or deviceID), and specify the skill-requirement to be "deviceName equal someConstant" or "deviceID equal someConstant".
Zeile 5:		Zeile 5:
	Also, virtual resources (such as database locks or other synchronization means) can be defined in such a way.		Also, virtual resources (such as database locks or other synchronization means) can be defined in such a way.

	The ~~followng~~ picture shows a block, which requires a device ~~capapble~~ of measuring voltage in the range -100V .. +		The following picture shows a block, which requires a device capable of measuring voltage in the range -100V .. +
	100V with an error of not more than 5%.		100V with an error of not more than 5%.

Ab am 1. April 2014 um 20:57 Uhr

2014-04-01T20:57:43Z

← Nächstältere Version		Version vom 1. April 2014, 20:57 Uhr
Zeile 1:		Zeile 1:
			Define resource requirements for the edited block here. Thesse are described by listing the required skills that a resource must have, in order to be useful for the block. The actual resource choice, allocation, reservation and freeing is done at execution time, by the built-in resource manager. The resource manager will fetch an appropriate resource-element from the inventory as present at execution time, reserve it, and allocate for use in the block for the time of the blocks execution. Other blocks which ask for a similar skill will either get another resource (if avaliable), or have to wait until that resource is released.

			Of course, direct resource allocation by name or id is a subset of the above described general mechanism: simply define a numeric or symbolic ID-skill (such as deviceName or deviceID), and specify the skill-requirement to be "deviceName equal someConstant" or "deviceID equal someConstant".

			Also, virtual resources (such as database locks or other synchronization means) can be defined in such a way.

			The followng picture shows a block, which requires a device capapble of measuring voltage in the range -100V .. +
			100V with an error of not more than 5%.

			[[Datei:blockRequirement1.jpg\|800px]]

			when executed, the built-in resource manager will allocate such a device from the inventory.

	The set of required resources which the action requires for its operation is defined in this editor. This set is not described by an explicit list of required resources, but instead by a list of skills which the allocated resource(s) must have.		The set of required resources which the action requires for its operation is defined in this editor. This set is not described by an explicit list of required resources, but instead by a list of skills which the allocated resource(s) must have.
	This gives expecco the flexibility to dynamically choose among a set of available resources, and decide at execution time, which device or operator is chosen.		This gives expecco the flexibility to dynamically choose among a set of available resources, and decide at execution time, which device or operator is chosen.

Ab am 1. April 2014 um 20:53 Uhr

2014-04-01T20:53:20Z

← Nächstältere Version	Version vom 1. April 2014, 20:53 Uhr
Zeile 1:	Zeile 1:
		The set of required resources which the action requires for its operation is defined in this editor. This set is not described by an explicit list of required resources, but instead by a list of skills which the allocated resource(s) must have.
		This gives expecco the flexibility to dynamically choose among a set of available resources, and decide at execution time, which device or operator is chosen.

Ab: Die Seite wurde geleert.

2014-04-01T20:50:17Z

Die Seite wurde geleert.

← Nächstältere Version		Version vom 1. April 2014, 20:50 Uhr
Zeile 1:		Zeile 1:
	[[Bild:SkillDescriptionEditor1.png\|thumb\|300px\|Keyword test editor]]

	This editor is used to describe the set of attributes a skill.
	Skills are used to describe the capabilities of a resource ([[ResourceDescriptionEditor \|see Resource Description Editor]])
	and also to define the requirements of an action ([[BlockDescriptionEditor \|see Block Description Editor]]).

	A skill is a collection of attributes which are typed values.
	For example, a skill might be "able to measure voltage".
	In this case, the set of values which make up this skill would be:
	* "minimum voltage"
	* "maximum voltage"
	* "error"
	all with a float datatype.

	== Add / Remove Skills ==
	You can add/remove skills attributes using the toolbar buttons or via the context menu.

	== Move Skills Up/Down ==
	You can move skill attributes up/down using the toolbar buttons or via the context menu.

	== Rename skill attributes ==
	To rename a skill attribute click with left mouse button on the Name field of a skill attribute. This will open an inplace editor in the selected table cell.


	In addition to real skills like the previous measurement skill,
	any device's attribute must be described using skills.
	<br>For example this can be ip-addresses, port numbers and device names:

	[[Datei:SkillDescriptionEditor2.png\|800px]]

	----
	For other editors see: [[Editors]]

	The full online documentation can be found under: [[Online Documentation]]