Description

Test Data Stories are a key part of GenRocket's Self Service Test Data Portal. We organize all the Test Data Story functionality into a part of the GenRocket platform we call "G-Stories."


Within the G-Stories platform, you can set up a suite of Test Data Stories, which can be used to further customize how test data is generated by GenRocket. Test Data Story Suites can only exist within a given Project Version of a Project. 



What is a G-Story Suite? 

  • A Test Data Story Suite or G-Story Suite is a set of Test Data Stories.


What are G-Stories? 

  • Test Data Stories (or G-Stories) are used to package individual Test Data Cases together with Scenarios, Scenario Chains, and Scenario Chain Sets.   


When should I use G-Stories?

  • When you want to use multiple Test Data Cases in combination with different Scenarios, Scenario Chains, and Scenario Chain Sets to generate complex test data.


How to Access and Manage G-Stories

  • Within a given Project Version, from the Project Versions Pane, expand the Self Serve Menu Options drop-down menu.

  • Next, select G-Stories within the menu.


How do Test Data Stories Work?


Step 1: Add a G-Story Suite to a Project Version

A G-Story Suite must be added to a selected Project Version of a given Project before G-Stories can be added and set up. A Project Version can have multiple G-Story Suites.
 


Step 2: Add G-Stories to the G-Story Suite

Each G-Story Suite can have multiple G-Stories. For simplicity, in the example below, the selected G-Story Suite contains only one G-Story. Each G-Story has its own chapters and chapter components. 



Note: Test Data Cases (or G-Cases) can be applied at the Story Level or the Chapter Level within a G-Story Suite. If a G-Case is applied at the Story Level, it will override any applied at the Chapter Level. 


Step 3: Add Chapters to each G-Story

A Chapter must have a unique title (CamelCase with no spaces) and contain at least one Chapter Component. Please note that the new Chapter will be added to the currently selected Story. Selected items are highlighted in blue. For this example, two chapters have been added to the selected G-Story.



Step 4: Add a Component to each Chapter within a G-Story

Each G-Story Chapter must have at least one Component, which can be one of the following: 

  • Scenario
  • (or) Scenario Chain
  • (or) Scenario Chain Set
  • (and optionally) Test Data Case


Note: The loopCount of the Test Data Case will override the Scenario loopCount value. For example, if the Scenario has a loopCount of 1 and the Test Data Case has a loopCount of 10, then 10 data records will be generated. 


populateOrg Chapter


populateCustomer Chapter


Step 5: (Optional) Set Parent/Sibling Relationships between G-Stories

Parent/Child Relationships can be set between G-Stories within a suite. A child Story will automatically inherit the Chapters and Components of the Parent. At least two G-Stories must be present to set up Parent/Child Relationships.


Click on the Inherit Story (Upward Arrow) icon to the right of each Story in the table to set Parent/Child Relationships.


When a G-Story has been set as the parent, it will be shown in the Parent Column.



Step 6: (Optional) Disable/Enable Chapters within a G-Story

When Parent/Child Relationships have been configured between G-Stories, Chapters within the Child Story may be disabled or enabled before generating test data.


Disabled Stories will not be used to generate test data when the G-Story is run in GenRocket Runtime. Use the toggles to enable or disable the desired Chapters.



Step 7: Download all Required Items for Generating Test Data

Important: We recommend setting up G-Repository before using G-Stories to generate test data. Several items must be downloaded to generate test data when using G-Stories. G-Repository ensures that the latest items are available without the user manually downloading them each time they need to generate data. 


To generate data using a G-Story, users would need to download the following if not using G-Repository: 

  • G-Story Suite
  • Scenarios
  • Scenario Chains
  • Scenario Chain Sets 
  • G-Case Suites


Step 8: Copy the Command for the G-Story Suite or G-Story

The command is located at the bottom of the G-Story Management Dashboard and will change depending on the selections made. Select a G-Story Suite or a G-Story and then copy the command line at the bottom of the dashboard



Step 9: Run the Command in a Command or Terminal Window

Paste the Command into a Command Prompt or Terminal window and press the Enter Key to generate test data.



Once test data generation has finished, you will see the following: 


Additional Information

The following articles can be used to learn more about the steps required to add and set up G-Stories:


Topic

Description

G-Stories Management Dashboard OverviewLearn more G-Stories Management Dashboard UI Components.
How to add a G-Story Suite to a Project VersionLearn about adding G-Story Suites to a Project Version.
How to add a Story to a G-Story Suite.Learn about adding G-Stories to a G-Story Suite.
How to add a Chapter to a G-StoryLearn about adding Chapters to G-Stories.
How to add a Component to a G-Story ChapterLearn about adding Components to G-Story Chapters.
How to set Parent/Child Relationships between G-StoriesLearn how to make a G-Story a parent to one or more G-Stories.
How to generate test data with G-StoriesLearn how to generate test data using G-Stories.