Description

A Scenario needs to be run within a Command Window or Terminal Session on your local computer. You will need to download the Scenario before completing the steps outlined below. 


The Scenario contains instructions for generating your test data including the type of RAW data to be generated, the number of records, and the type of generated output data (delimited file, fixed file, JSON, etc.). 


In This Article


How to Run a GenRocket Scenario

Open a Command Window or Terminal Session. Navigate to the directory location of the downloaded Scenario.


Enter the following command and replace <ScenarioName> with the name of the Scenario you are running.


genrocket -r <ScenarioName>.grs


Note: The following articles can be referenced for running a Scenario when using G-Repository and/or GMUS, or an API call: 


GenRocket Engine Sequence Execution of a Scenario

The diagram below shows the sequence and components the GenRocket engine uses to load and execute a Scenario to generate synthetic test data.

  • GenRocket Engine - The engine loads and runs a Scenario
  • GenRocket User Profile - Used by the engine to validate the user
  • GenRocket Scenario - Contains instructions to generate synthetic data
  • GenRocket Cloud License Server - Validates a user’s permission to run a Scenario



Data Loading Status Reports (Database Insertion)

When GenRocket Scenarios are run from the Command Line, and data fails to load, an exception will be thrown and will be returned back to the Command Line. So when a Scenario runs and the data is correctly inserted into the database the user will know it was successful because there is no exception reported back to the Command Line and will know there was a problem because an exception was returned to the command line.


When GenRocket Scenarios are run within a testing framework as part of an automated testing process, and there is a data load failure, an exception will be thrown and the exception will be returned back to the testing framework. So the user will know when the data is correctly inserted into the database or not by viewing the reports in the testing framework.