In the Test phase, you can run and test Client Commands. If the test fails, you can revert the Client Command to the Create phase with a button or the context menu. Otherwise, you can transfer the Client Command to the Synchronization phase with a button or the context menu.
Test phase
The Client Commands that are currently in the Test phase are displayed in the console. These commands are displayed with the same properties as in the Creation phase. In the top drop-down list you can also have all Client Commands or all Client Commands with Released status (phase 4) displayed.
To test a Client Command, you need test clients. With the Configure test environment icon you can view and even edit a list of all test clients. With corresponding buttons you can Update lists, Add and Remove test clients, and test Client Commands.
Note: |
Clients, which have been added as test clients, always draw their data directly from the ACMP server. This applies not only to Client Commands which are to be tested but also to all other Client Commands and updates. Therefore, you should select only clients which have a sufficient bandwidth to the server. |
Client Command properties |
|
|
Console script Part of the Client Command runs in the ACMP Console. |
|
Client script Part of the Client Command runs on the client. |
|
Released The Client Command has at least one released version. |
|
Protected The Client Command is protected by a password. |
|
Interactive The Client Command can be run from the CommandLauncher. |
|
Run as a task The Client Command is configured as an Agent Task. |
Add Test Client
To add a test client, click on the button. It opens a wizard with a view which is similar to the query management (see Query Management). Here you can run all queries of the Query management . Then select one or more test clients and click the Add button.
You can remove test clients by selecting the test client concerned and then clicking Remove clients. Due to the enabled checkboxes behind the client names potential conditions (e.g., If operating system is (not)) of the Client Command will be ignored. In this way, Client Command versions can also be tested, if their set conditions are not able to fulfill the requirements of the test environment (e.g., is user in group).
Note: |
For test clients, use systems that come as close as possible to the target platform in regard to hardware and software equipment In this way, you can ensure that the test results are significant for the production environment. |
Test Client Command
To test a client command, click on the Run icon. In the dialog that opens, you can select Client Commands you want to test from a drop-down list. Move the selected Client Commands to the right column wit drag & drop or with the corresponding buttons. Client Commands, which you selected before calling the dialog, are moved automatically to the right column.
In the second step, you can now select the test client on which the Client Commands are to be tested. By clicking on OK you can start the tests.
Test result
On the right-hand side, all tests executed with the currently marked Client Command are listed. At the same time, the test clients on which the test is executed are listed along with the tested version. In addition, the date of each test can be viewed, as well as an icon indicating if the test was successful or not. With the log icon, you can view the test log of each test.
Last change on 10.03.2014