Scenarios

testgrinder service will be discontinued on January 31, 2025

A scenario is a unit of work for testgrinder. When you kick off a testgrinder run each scenario will be executed independently of other scenarios in the run.

In testgrinder related scenarios are grouped into scripts and edited together. The idea here is that you put scenarios testing a particular system feature or performing similar tasks together in one place. You may think of testgrinder scripts as analogous to files. If you ever export testgrinder project to an external git repository, you will see that testgrinder will export each script as a separate file.

You further organize related scripts into projects, optionally using folders to help manage projects with lots of scripts.

Here's an example of a script consisting of two scenarios:

Script: Assets
  
 	Scenario: Assets - Create Asset

   	Given I login to Maximo as User
      And I go to the Assets / Assets application
     
     When I click the 'New Asset' toolbar button
      And I enter 'Test Asset' in the description field of the Asset field
    
    Then I successfully save the record
     And I logout
  
 	Scenario: Assets - Actions - Change Status - Active

   	Given I login to Maximo as User
      And I go to the Assets / Assets application
      And I click the 'New Asset' toolbar button
      And I enter 'Test Asset' in the description field of the Asset field
      And I successfully save the record
      
     When I select action 'Change Status'
      And I select Active in the dropdown list for the 'New Status' field
      And I click the OK button
      
     Then I see the value ACTIVE in the Status field
      And I logout

When executing a run with this script, testgrinder will execute the two scenarios independently. Since scenarios are written as independent of each other, this enables testgrinder to run them independently thus greatly reducing the total run time.