The menu “TEST” of the Designer aims at providing a Quality Assurance process. As such, it aims at providing a complete functional validation environment to the person which is modeling in the Designer.

Definition: A Test Campaign is a functional module that allows for the testing, debugging and validation of run-time projects (such as Configurable Projects) built with the Designer.

Definition: A Test Case (TC) represents a typical use case to be tested whenever a new version of a project is to be deployed. Each test case can be (re-)used in multiple Test Campaigns. Each test case describes the steps to be run through and the expected results.

The following functions are a part of Test Campaign:

• Recording a configuration When a configuration model has been (partially) completed, it will have to be tested in order to validate its quality before versioning it and deploying to a production environment. Test Campaign allow recording the user actions in the Configurator user interface.
• Specifying extra controls once the configuration has been recorded, or during the original recording session, extra controls might have to be added to the test case. These controls, which are referenced as “assertions”, can be done by “browsing” the configuration session and dragging and dropping (or building) extra CPEs to specific locations in the test case.
• Conducting a test run Once the test case has been recorded, regardless of the fact if extra controls have been specified, a test run can be conducted. The test run will simulate a Configurator user interface by executing all actions stored in the recorded file. These actions can correspond to user actions (setting a value, inserting a loop, etc.) or to extra controls (checking a value). The end-result of a test run is a collection of states (passed/failed) that indicate if the test run has been successful or not.
• Debugging a test run once the test run has been conducted, and if errors have arrived, the test run can be inspected (debugged). The inspection allows obtaining additional important information such as the server log information or even the values of all CPE in memory.
• Conducting performance tests once the test run executes well (for a single user), it will be possible to launch a performance test.

The test campaign menu is accessible by clicking on TEST on the Designer Dashboard:

From this screen, you can:

• Visualize the existing Test Campaigns
• Run one or all existing Test Campaign(s)
• Create a New Test Campaign

By clicking on an existing test campaign, the following steps allow you to edit:

• Test Case: This step allows creating multiple test cases inside the campaign structure. The content of a test case (a list of actions) can be created either manually (by adding lines and CPE) or recorded automatically. Also, this step will allow defining a certain number of goals, such as latency times and performance goals.
• Debug: This step allows running & debugging a given test case (or a test campaign). During the test run, the Designer will indicate the progress of the test case/campaign run, will show the status of each action and/or control and will allow the modeling user to debug the test run, by generating log files and memory snapshots. This step also allows adding a number of additional

  controls that might be necessary to better understand the model or to enforce quality.

• Run: This step allows running a performance/stress test for a given test case, or for a test campaign.