Create scenarios

Definition

A scenario is a sequence of steps that represents a behavior of the application as expected by the user. It should focus on the goal of the test rather than expressing UI level interactions. A scenario may be either manual and/or automated. In agile project, a user story is typically associated with one or more Hiptest scenarios.

Scenario page

scenario-page

A scenario is defined by different data:

  • Name: the name of a scenario is unique within a given project.
  • Folder path: path of the folder that contains the scenario. See Project organisation section.
  • Description: Field text used to add a description. See Description formatting section.
  • Tags: you can add tags to a scenario. The search feature from the scenario page can be used to search for scenarios based on tags (as well as folders). See Project organisation section.
  • Attachments: you can attach many files to the scenario by clicking on the button  ‘Add attachment’ or  by using the drag-and-drop function.
  • Datatable: you can add parameters to a scenario and define several datasets with the Datatable. See Datatable section.

Step editor

The step editor is a feature we have particularly invested on to enhance test authoring. Steps of a scenario can be either:

  • an action step_action: “Log in with default account”
  • a result step_check: “check that user is logged in
  • Action Word step_AW: See Action word section.

The step editor comes along with a powerful suggestion capability that enables you to reuse existing steps and streamline the design of scenarios.

Voila_Capture 2015-08-07_09-23-54_AM

Parameters

You can add parameters to your scenario with the datatable. It will enable you to generate several tests with different datasets for a given scenario.

To include a parameter in a step (being an action or result), use the following syntax: ${param_name}. For example, if you have UserName as parameter of your scenario, you can write the following step: login with ${UserName} to the application.

Actions on steps

  • To move/reorder a single step, click on the step number and do drag&drop. You can use as well the arrows on the right step_arrows.
  • To delete a step, just click on the icon step_delete
  • You can also select a group of steps, move it, delete it or promote it into an action word step_AW (see refactoring section)

Voila_Capture 2015-08-07_09-25-29_AM

Execution summary

Voila_Capture 2015-08-07_09-48-11_AM

Just bellow the step editor you have access to the different execution status of your scenario organized by test run.

Other actions available on a Scenario

Voila_Capture 2015-08-07_09-45-32_AM

You can apply the following actions to a scenario:

  • Clone: to duplicate the scenario. You will have to select the destination folder.
  • Add to test run: to add the current scenario to an existing test run and execute it.
  • Move: to move the scenario from the current folder to the selected folder.
  • Delete: to delete the scenario. Be carefull, you will not be able to restore it.