Starting a scenario

After creating a scenario in IBM® DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), you can start it.

Optional: To prevent other users from interrupting your testing, lock the environment that you are using. If you lock the currently selected environment, the locked status message is displayed on the Environments Dashboard.
  1. Log in to Test Virtualization Control Panel.
  2. Click the Environments icon or navigation link.

    The Environments Dashboard is displayed.

  3. You can change the domain and environment you want to view by clicking the domain/environment link, and from the domain/environment selection dialog displayed, select the domain, and then select the Environment.
    The Environments Dashboard is displayed for the selected environment and domain.
    Note:
    If you are using 8.5.1.1 or later and domain-level security is enabled, you can use only the domains to which you were granted access.
  4. Identify the scenario you want to start.
    Note:

    You can identify a scenario on the Environments Dashboard from the Start Scenario icon (image of the icon) that is present for a scenario, while the stub can be identified from the Start stub icon (image of the icon) it has.

  5. For the scenario you want to start, click the Start icon (image of the icon) on the Environments Dashboard.
    Note:
    All the stubs that were running when you created the scenario can be seen included under the new scenario.

The scenario starts. The status of the scenario changes from STOPPED to STARTING or RUNNING.

In 8.5.1 or later:
  • If a scenario tries to start more instances of a stub than there are available agents (for example, four stub instances on three agents), Test Virtualization Control Panel displays a message about insufficient agents and problems. If you choose to ignore these problems and continue, the number of stub instances started will equal the number of available agents, which will be less than the number of stub instances saved in the scenario.
  • If you have multiple subs in a scenario and each stub has multiple instances that are configured to run on multiple agents (for example, two stubs, each with three instances, and configured to run on three agents), Test Virtualization Control Panel will start the scenario and not display any messages if the required number of agents is available. This is because separate stubs in a scenario are treated independently of each other and because scaling out applies to multiple stub instances and not to multiple stubs.