What improvements to Scenario Outlines should I be aware of?

What improvements to Scenario Outlines should I be aware of?

What do we know about Scenario Outlines?

Scenario Outlines are similar to regular Scenarios except that a Scenario Outline executes multiple times, once for each row of data it is using.

What is staying the same?

  • The keyword Scenario Outline:
  • The ability to use the Examples section after the last Step in the Scenario to generate data for the iterations of the execution
  • Values replacing tokens with a format of <FIELD NAME>, aka chevron variables.
  • A Scenario Outline still executes once for each row of values

What has been added?

Scenario Outlines can now utilize multiple external data sources to dynamically generate rows of values. This will provide an easier and more efficient path to increase test parameter coverage.

The new data sources included are CSV files, SQL queries, MOCA queries and Cycle's Data store. In addition, there is a Example Row: input that creates a single iteration for parameter and script building. The links to the KB articles specific to each source’s set up and usage can be found below.

New functionality has been added for saving and reusing named Connection and Credential values.

Scenario Outline sources requiring connection and credential information will use the named values stored in Cycle.

For instructions on setting up Connections and Credentials check out this KB article.

4 new steps have been created to improve Scenario Outline usage

  • I assign chevron variables "<COMMA_SEPARATED_VARIABLE_NAMES>" to dollar variables

    • Assigns the listed current chevron variables <variable> to dollar variables $variable. The new dollar variables will have the same names as the chevron variables.
    • EXAMPLE:  Given I assign chevron variables "name, age, place" to dollar variables
  • I assign all chevron variables to dollar variables

    • Assigns all chevron variables <variable> to dollar variables $variable. The new dollar variables will have the same names as the chevron variables.
    • EXAMPLE: Given I assign all chevron variables to dollar variables
  • I assign chevron variables "<COMMA_SEPARATED_VARIABLE_NAMES>" to unassigned dollar variables

    • Assigns the listed current chevron variables <variable> to dollar variables $variable that are not otherwise assigned. The new dollar variables will have the same names as the chevron variables.
    • EXAMPLE:  Given I assign chevron variables "name, age, place" to unassigned dollar variables
  • I assign all chevron variables to unassigned dollar variables

    • Assigns all chevron variables <variable> to dollar variables $variable that are not otherwise assigned. The new dollar variables will have the same names as the chevron variables.
    • EXAMPLE: Given I assign all chevron variables to unassigned dollar variables
    • Related Articles

    • How to use a CSV file as a Scenario Outline data source

      With the enhancements to Scenario Outlines, it is now possible to use multiple sources for test parameter data. Previously, parameters were set in the Feature in an Examples section specified and maintained by the user. The addition of Example Row, ...
    • How to use a SQL query as a Scenario Outline data source

      With the enhancements to Scenario Outlines, it is now possible to use multiple sources for test parameter data. Previously, parameters were set in the Feature in an Examples section specified and maintained by the user. The addition of Example Row, ...
    • How to use Datastore Examples as a Scenario Outline data source

      With the enhancements to Scenario Outlines, it is now possible to use multiple sources for test parameter data. Previously, parameters were set in the Feature in an Examples section specified and maintained by the user. The addition of Example Row, ...
    • How to store Connections and Credentials in Cycle

      Cycle 2.5 includes the ability to save Connections and Credentials for your systems under test. Using named Connections and Credentials streamlines and simplifies declaring system access, makes Features look cleaner and promotes reusability of “set ...
    • How to use Example Row as a Scenario Outline data source

      With the enhancements to Scenario Outlines, it is now possible to use multiple sources for test parameter data. Previously, parameters were set in the Feature in an Examples section specified and maintained by the user. The addition of Example Row, ...