Wiki source code of Client Command testen

Last modified by Sabrina V. on 2026/07/31 06:19

version	line-number	content
1.1	1	{{aagon.floatingbox/}}
	2
39.2	3	In the //Testing// phase, you can execute and test Client Commands on selected clients. If the test fails, you can move the Client Command back to the //Create// phase using a button or the context menu. Otherwise, you can move the Client Command to the //Synchronize// phase using a button or the context menu.
1.1	4
	5	{{figure}}
7.1	6	[[image:36_64_Client Commands_Testen Übersicht_1637.png\|\|alt="34_64_ClientCommands_ClientCommanderstellen_1337.png" data-xwiki-image-style-alignment="center"]]
1.1	7
	8	{{figureCaption}}
39.2	9	Testing phase
1.1	10	{{/figureCaption}}
	11	{{/figure}}
	12
39.2	13	The Console lists the Client Commands that are currently in the //Test// phase. These are displayed with the same properties as in the //Creation// phase. Using the drop-down list at the top, you can also display all Client Commands or display only those with the status //Released// (Phase 4).
1.1	14
39.2	15	To test a client command, you need test clients. Using the //Test Environment// icon, you can view and edit a list of all test clients. Using the corresponding buttons, you can //refresh// the list, //add// and //remove// test clients, and test client commands.
1.1	16
	17	{{aagon.infobox}}
39.2	18	Clients added as test clients always retrieve their data directly from the ACMP Server. This applies not only to Client Commands to be tested but also to all other Client Commands and Updates. Therefore, you should only select clients that have sufficient bandwidth to the Server.
1.1	19	{{/aagon.infobox}}
	20
39.2	21	= Client Command Properties =
1.1	22
	23	\|(((
28.1	24	[[image:XWiki.Images.WebHome@script_console.png\|\|alt="Script_Console" data-xwiki-image-style-alignment="center" height="32" width="32"]]
1.1	25	)))\|(((
39.2	26	Part of the client command is executed in the ACMP Console.
1.1	27	)))
	28	\|(((
28.1	29	[[image:XWiki.Images.WebHome@script_client.png\|\|alt="Script_Client" data-xwiki-image-style-alignment="center" height="32" width="32"]]
1.1	30	)))\|(((
39.2	31	Part of the client command is executed on the client.
1.1	32	)))
	33	\|(((
28.1	34	[[image:XWiki.Images.WebHome@clientcommandphase_release.png\|\|alt="ClientCommandPhase_Release" data-xwiki-image-style-alignment="center" height="32" width="32"]]
1.1	35	)))\|(((
39.2	36	The client command has at least one released version.
1.1	37	)))
	38	\|(((
7.1	39	[[image:SelectiveSync.ico\|\|data-xwiki-image-style-alignment="center"]]
1.1	40	)))\|(((
39.2	41	The client command can only be synchronized with selected file repositories.
1.1	42	)))
	43	\|(((
7.1	44	[[image:clientcommand_interactive.png\|\|alt="ClientCommand_Interactive" data-xwiki-image-style-alignment="center"]]
1.1	45	)))\|(((
39.2	46	The client command can be executed via the ACMP Kiosk.
1.1	47	)))
	48	\|(((
7.1	49	[[image:PassWord_Locked.ico\|\|data-xwiki-image-style-alignment="center" height="32" width="32"]]
1.1	50	)))\|(((
39.2	51	The Client Command is password-protected.
1.1	52	)))
	53
39.2	54	= Add Test Clients =
1.1	55
39.2	56	To add a test client, click the //Test Environment// button. A wizard opens with a view similar to the [[Query Management>>doc:ACMP.69.ACMP-Solutions.Client-Management.Abfrageverwaltung.WebHome]] interface. Here, you can execute all Queries from Query Management. Then select one or more test clients and click the //Add// button.
1.1	57
	58	(% style="text-align:center" %)
28.1	59	[[image:XWiki.Images.WebHome@hmfile_hash_56c97942.png\|\|alt="Testumgebung konfigurieren" height="279" width="502"]]
39.2	60	Configure the test environment
1.1	61
39.2	62	You can remove test clients by selecting the corresponding test client and then clicking //Remove Clients//. Checking the checkboxes next to the client names causes any conditions (such as “If operating system is (not)”) in the Client Command to be ignored when testing the command on the corresponding client. This also allows you to test Client Command versions whose configured conditions you cannot meet in the test environment (e.g., “is user in group”).
1.1	63
	64	{{aagon.infobox}}
39.2	65	Use systems as test clients whose hardware and software configurations are as close as possible to those of the target platforms. This ensures that the test results are meaningful for the production environment.
1.1	66	{{/aagon.infobox}}
	67
21.1	68	{{aagon.infobox}}
39.2	69	Note that clients located in the test environment execute the highest possible phase of the Client Command. This also applies to jobs running on clients that are not on the test interface.
21.1	70	{{/aagon.infobox}}
	71
1.1	72
	73
39.2	74	= Testing a Client Command =
1.1	75
39.2	76	To test a Client Command, click the //Execute// icon. In the dialog that opens, you can select the Client Commands to be tested from a list. Move the selected Client Commands to the right column. You can do this via drag-and-drop or using the corresponding buttons. Client Commands that were selected before the dialog was opened are automatically added to the right column.
1.1	77
39.2	78	In the second step, you can now select the test clients on which the Client Commands will be tested. Click //OK// to start the tests.
	79
	80	= Test Results =
	81
	82	On the right-hand side, all tests executed with the current Client Command are listed. The test clients on which the test was run are listed along with the version being tested. Additionally, the time of each test is displayed, along with an icon indicating whether the test was successful or not. You can view the test protocol for each test by clicking the protocol icon.