In order to create a new test campaign, proceed as follows:

How-To From the Dashboard:

• [In the Dashboard]
  • Click on TEST
• [In the menu toolbar]
  • Click on New
• [In the popup]
  • Enter a name and a description and click on Create
    • The test case is added to the list

In order to create a new test case, proceed as follows:

How-To:

• [In the explorer]
  • Select the test campaign
• [In the menu toolbar]
  • Click on '+' and select Test Case
• [In the popup]
  • Enter a name and a description
  • Click Add
    • The test case is added to the explorer

In order to record a test case, proceed as follows:

How-To:

• [In the explorer]
  • Open the test case by clicking on its text
• [In the menu toolbar]
  • Click on Start Recording
• [In the popup]
  • Choose or upload a layout file
  • Choose or upload a configuration file
  • Tick the checkbox in order to empty the cache if necessary
  • Click OK
    • The Configurator opens
      
      
      • [In the Configurator]
        • Execute the use case that has to be tested by providing all the answers to the user dialog.
        • Close the Configurator when finished and return to the Designer.
      • [In the popup "Recording in progress"]
        • Click Stop
          • The configuration actions are gathered and the test case is updated.
      
      • [In the menu toolbar]
        • Save
• LatencyThe latency is the "wait time" (the time the engine has been inactive) between the recorded action and the previous one. The latency simulates the "think time" of the recording user. The recorded latency can later on be reused for performance tests taking into account "realistic" user think times.
• Reference performanceThe reference performance is the "response time" from the engine, between the moment it received a command (setValue for instance) and the moment it issued the result. The reference performance can be reused later on to compare with performances registered when the model has undergone some changes.

Different kinds of actions can be added to the test case:

Action

These are actions which can be undertaken by the engine itself to, for instance, set a value, reset a value, or automatically complete the configuration.

Debug

These are assertions which are meant to check the value of a CPE or its domain. These actions are typically used to enforce the quality during the validation campaign.

Navigation

These are actions which are typically requested by the user interface to navigate from one object to another. These actions can typically trigger the initial load of some objects.

Observation

These are actions which are meant to inform the Configurator user interface or any other external watching entity that some changes have occurred and that it needs to be updated.

In order to manually add actions to a test case, proceed as follows:

How-To:

• [In the explorer]
  • Open the test case by clicking on its name
• [In the test case table]
  • Select the line before or after which you want to add an action
• [In the menu toolbar]
  • Click on insert line
• [In the popup]
  
  
  • Choose an action type (observation, debug, navigation or action)
  • Choose an action (this list depends on the action type)
    • A default XML representation for this action is generated
    • In the XML representation, replace all default CPE by the target CPE. In order to achieve that, position the cursor inside the CPE. The CPE will now appear in the CPE Builder. Modify the CPE in the CPE Builder and click “Update” when the target CPE is complete.
    • In the XML representation, replace all default values by target values (e.g. “ValueToAssert” for an “AssertValue” action).
  • Click OK
    • The new action is now added to the test case.
• [In the menu toolbar]
  • Save

In order to completely modify the type of action and its content, proceed as follows:

How-To:

• [In the explorer]
  • Open the test case by clicking on its name
• [In the test case table]'
  • Select the line corresponding to the action to be modified
• [In the menu toolbar]
  • Click on update line
• [In the popup - see above]
  • Choose an action type (observation, debug, navigation or action)
  • Choose an action (this list depends on the action type)
    • A default XML representation for this action is generated
    • In the XML representation, replace all default CPE by the target CPE. In order to achieve that, position the cursor inside the CPE. The CPE will now appear in the CPE Builder. Modify the CPE in the CPE Builder and click “Update” when the target CPE is complete.
    • In the XML representation, replace all default values by target values (e.g. “ValueToAssert” for an “AssertValue” action).
  • Click OK
    • The line has now been updated.
• [In the menu toolbar]
  • Save

In order to modify the action’s content only, proceed as follows:

How-To:

• [In the explorer]
  • Open the test case by clicking on its name
• [In the test case table]
• [In the popup - see above]
  • In the XML representation, replace all CPE by a new target CPE. In order to achieve that, position the cursor inside the CPE. The CPE will now appear in the CPE Builder. Modify the CPE in the CPE Builder and click "Update" when the target CPE is complete.
  • In the XML representation, replace all values by new target values (e.g. "ValueToAssert" for an "AssertValue" action).
  • Click OK
    • The action is now updated.
• [In the menu toolbar]
  • Save

In order to delete an action in a test case, proceed as follows:

How-To:

• [In the explorer]
  • Open the test case by clicking on its description
• [In the test case]
  • Select the line corresponding to the action to be deleted
• [In the menu toolbar]
  • Click on Delete line
• [In the menu toolbar]
  • Save

In order to delete a test case, proceed as follows:

How-To:

• [In the explorer]
  • Select the test case to be deleted
• [In the menu toolbar]
  • Click on Delete
• [In the menu toolbar]
  • Save

In order to export a test case, proceed as follows:

How-To:

• [In the explorer]
  • Open the test case to be exported
• [In the menu toolbar]
  • Click on Export
• [In the popup]
  
  
  • Choose the file encoding
  • Click OK

In order to import a test case, proceed as follows:

How-To:

• [In the explorer]
  • Make sure that a new, empty test case is available
  • Open the test case in which the script has to be imported
• [In the menu toolbar]
  • Click on Import
• [In the popup]
  
  
  • Choose the file to be imported
  • Click OK