Description

Our Self Service Test Data Portal can be used to achieve complex, enterprise-level test data objectives based on five core agile-driven platforms within the application: 

  • G-Cases - Test Data Cases (TDC)
  • G-Rules - Test Data Rules (TDR)
  • G-Queries - Test Data Queries (TDQ)
  • G-Stories - Test Data Stories (TDS)
  • G-Epics - Test Data Epics (TDE)


When should you use the Self Service Test Data Portal? 

  • Any time you want to generate and validate complex, synthetic test data using Test Data Epics, Test Data Stories, Test Data Cases, Test Data Rules, and/or Test Data Queries.


How do you use the Self Service Test Data Portal? 

Each platform builds upon defined base Domains and Attributes with a Project. Test Data Epics, Stories, Cases, Rules, and Queries are created for a given Project Version within a Project. The following provides quick look at the Self Service Test Data Portal workflow:

  1. Create a Test Data Case Suite with Categories and Cases
  2. (Optional) Create Test Data Queries to query real data from databases
  3. (Optional) Create Test Data Rules to apply business logic during test data generation
  4. (Optional) Add Test Data Rules and Queries to Test Data Cases
  5. Create Test Data Story Suites with Stories and Chapters
  6. Create Story Epics with Stories from multiple Test Data Story Suites


Note: Test Data Cases can be applied at the Test Data Epic Level, Test Data Story Level, and the Chapter Level within Test Data Stories. 

  • Cases applied at the Epic Level override any cases set at the Story Level. 
  • Cases applied at the Story Level override those assigned to Chapters within the Story.


Self Service Test Data Portal Diagram



In This Article


G-Cases - Test Data Cases

The G-Cases platform can be used to create a suite of Test Data Cases. Within each suite, you can set up multiple testing Categories (Load, Unit, Negative, Integration, etc.) and define individual Test Data Cases within each category. 


Each individual Test Data Case can also have added Test Data Rules and Queries, which are applied when the Test Data Case is run by GenRocket Runtime. 


Simple Workflow Example for Test Data Cases

Here is a sample tree view showing a simple workflow for Test Data Cases:

  • Test Data Case Suite 1
    • Category (Load)
      • Test Data Case 1
      • Test Data Case 2
    • Category (Unit)
      • Test Data Case 1
      • Test Data Case 2
  • Test Data Case 2
    • Category (Integration)
      • Test Data Case 1
      • Test Data Case 2


Here is the same tree view shown above as a workflow diagram:


Using Rules and Queries with Test Data Cases

Test Data Rules and Queries can be added to a Test Data Case and applied when the Test Data Case is run by GenRocket Runtime. 


Here is a tree view showing a simple workflow for Test Data Cases with added Test Data Rules and Queries:

  • Test Data Case Suite 1
    • Test Data Category 1
      • Test Data Case 1
        • Test Data Rules 1
      • Test Data Case 2
        • Test Data Query 1
    • Test Data Category 2
      • Test Data Case 1
        • Test Data Rules 1
        • Test Data Rules 2
        • Test Data Query 1
        • Test Data Query 2


Here is the same tree view shown above as a workflow diagram:



Generating Test Data with Test Data Cases

Test Data Cases can be run manually by running the corresponding command line in a Command or Terminal Window. GenRocket also offers options for automating this process. Test Data Cases can be used to generate test data in two ways: 

  • Run on their own with a downloaded Scenario, ScenarioChain, or ScenarioChainSet in GenRocket Runtime
  • Assigned to and applied when a Test Data Story or Epic is run in GenRocket Runtime

Note: Any added Rules or Queries will be employed automatically during test data generation when added to the Test Data Case.


Note: For more information about configuring and using Test Data Cases, click here.


G-Rules - Test Data Rules

The G-Rules platform can be used to create a suite of Test Data Rules that can run by GenRocket Runtime with a Scenario, ScenarioChain, or ScenarioChainSet (or) added to an individual Test Data Case. 


Test Data Rules apply business logic as a conditional if-then statement during test data generation for defined Domains and Attributes. 


Simple Workflow Example for Test Data Rules

Here is a tree view showing a simple workflow for a Test Data Rule Suite:

  • Test Data Rule Suite 1
    • Test Data Rule 1
      • Condition
      • Action
    • Test Data Rule 2
      • Condition and/or Condition
      • Action
    • Test Data Rule 3
      • Condition
      • Action
    • Default Rule
      • Action

Here is the same tree view shown above as a workflow diagram:



Generating Test Data with Test Data Rules

Test Data Rules can be run manually by running the corresponding command line in a Command or Terminal Window. GenRocket also offers options for automating this process. Test Data Rules can be used to generate test data in two ways: 

  • Run on their own with a downloaded Scenario, ScenarioChain, or ScenarioChainSet in GenRocket Runtime
  • Added to an individual Test Data Case and applied when the Test Data Case is run in GenRocket Runtime


Note: For more information about configuring and using Test Data Rules, click here.


G-Queries - Test Data Queries

The G-Queries platform can be used to create a suite of Test Data Queries that can be run by GenRocket Runtime on their own with a Scenario, ScenarioChain, or ScenarioChainSet (or) added to an individual Test Data Case. The following can be queried for real data using the G-Queries platform.

  • SQL Databases
  • NoSQL Databases
  • CSV Files


Test Data Queries query a database for real data and then blend it with generated synthetic data. For example, you could query a Customer Database for each customer's first and last name and then blend that data with the following synthetically generated data values:

  • address
  • city
  • state
  • zip code
  • date of birth
  • SSN


Sample SQL Query with Retrieved Data

select id, first_name, last_name, middle_initial,
email_address, department_id, role_id, password
from user
where department_id = 2;



Generating Test Data with Test Data Queries

Test Data Queries can be run manually by running the corresponding command line in a Command or Terminal Window. GenRocket also offers options for automating this process. Test Data Queries can be used to blend data with synthetically generated test data two ways: 

  • Run on their own with a downloaded Scenario, ScenarioChain, or ScenarioChainSet in GenRocket Runtime
  • Added to an individual Test Data Case. The query will occur when the Test Data Case is run in GenRocket Runtime


Note: For more information about configuring and using Test Data Queries, click here.


G-Stories - Test Data Stories

The G-Stories platform can be used to create one or multiple suites of Test Data Stories with their own Chapters and Chapter Components. Each Chapter can have a Test Data Case and a Scenario, ScenarioChain, or a ScenarioChainSet. 


Test Data Stories can be used to package multiple Test Data Cases with defined Scenarios, Scenario Chains, and/or ScenarioChainSets. Test data can then be generated for a Test Data Story Suite or an individual Test Data Story by running a single command line in GenRocket Runtime. 


Simple Workflow Example for Test Data Stories

Here is a tree view showing a simple workflow for a Test Data Story Suite that does not contain Test Data Cases:

  • Test Data Story Suite
    • Test Data Story 1
      • Chapter 1
        • Scenario 1
      • Chapter 2
        • Scenario 2
      • Chapter 3
        • ScenarioChain 1
    • Test Data Story 2
      • Chapter 1
        • ScenarioChain 2
      • Chapter 2
        • ScenarioChainSet 1


Here is the same tree view shown above as a workflow diagram:



Using Test Data Cases with Test Data Stories

Test Data Cases can be can be assigned and applied at these two levels within a Test Data Story Suite: 

  • Story Level - Applied to the whole story and will override any cases assigned within that story's chapters.
  • Chapter Level - Applied for that chapter only and do not impact other chapters or the story as a whole. 


Here is a sample tree view showing a simple workflow example for Test Data Stories with assigned Test Data Cases:

  • Test Data Story Suite 1
    • Story 1 (Test Data Case 1)
      • Chapter 1
        • Test Data Case 2
        • Scenario 1
      • Chapter 2
        • Test Data Case 3
        • Scenario 2
      • Chapter 3
        • ScenarioChain 1
    • Story 2
      • Chapter 1
        • Test Data Case 4
        • ScenarioChain 2
      • Chapter 2
        • Test Data Case 5
        • ScenarioChainSet 1


Here is the same tree view shown above as a workflow diagram:



Note: A Test Data Case assigned at the Story Level overrides any cases assigned to individual chapters within a story. The image above is designed to provide an overview of how Test Data Cases can be assigned within a suite of Test Data Stories. 


Generating Test Data with Test Data Stories

Test Data Story Suites and Stories can be run manually by running the corresponding command line in a Command or Terminal Window. GenRocket also offers options for automating this process. Test Data Stories can be used to generate test data in three ways:

  • Run the entire Test Data Story Suite in GenRocket Runtime
  • Run an individual Test Data Story in GenRocket Runtime
  • Disable and Enable Chapters prior to running the Test Data Story Suite or Story in GenRocket Runtime


G-Story Epics - Test Data Epics

The G-Story Epics platform can be used to organize and run Test Data Stories from multiple Test Data Story Suites at the same time through GenRocket Runtime. A Test Data Epic can look at a particular Test Data Story within a suite to generate test data. 


Individual Test Data Stories can be combined to generate more complex test data. For example, Test Data Stories can be combined to populate an entire database based on defined test data cases using a single command line. 


Simple Workflow Example for Test Data Epics

Here is a sample tree view showing a simple workflow example for Test Data Epics:

  • Test Data Epic
    • Test Data Story 1
    • Test Data Story 2
    • Test Data Story 3

Here is the same tree view shown above as a workflow diagram:



Generating Test Data with Test Data Epics

Test Data Epics can be run manually by running the corresponding command line in a Command or Terminal Window. GenRocket also offers options for automating this process.