Description

This article will walk you through every step for generating test data from EDI Projects in the GenRocket web platform. It will cover the following steps: 


Step 1: Set up GenRocket VPC Runtime

Users must set up the GenRocket VPC Runtime before EDI Test Data can be generated. The steps for this process vary per operating system, and links are provided below: 

           

Step 2: (Optional) Set Up Your Database Connection Properties File

A Database Connection Properties File can be used on the user's local machine to connect to a database. A database connection allows individual users to retrieve data from and populate tables within the connected database. 


Users wanting to connect to a database must create a Database Connection Properties File on their local machine. The format for the file is shown below: 


driver=<JDBCDriverClassName>
user=<userToConnectToDatabase>
password=<passwordToConnectToDatabase>
url=<URL>/<databaseName>
batchCount=1000


Note: The detailed steps of this process can be found in this knowledge base article: How do I connect GenRocket Runtime to a Database?


An Organization Admin or a Team Manager will need to add a new Database Resource to the GenRocket web platform if it has not already been added. 


Once added, each user will see the new Database Resource and can edit the value as needed for their local machine. The Database Resource is shared by the Organization; however, the value is User-specific and will vary per user.



Note: The detailed steps of this process can be found in this knowledge base article: How do I connect GenRocket Runtime to a Database?


Step 3: Set up Resources in the GenRocket Platform

Resources within the GenRocket web platform must be appropriately configured to download your EDI Configuration, Scenario Chain Sets, Test Data Cases, etc. 


Every user must have the following two resources configured on their local machine: 

  • resource.home.directory - Defines the home directory on your local computer.
  • resource.output.directory - Defines the directory where generated files will be saved.

     

If you plan to retrieve data or populate tables within a connected database, you will need to enter the path of the Database Connection Properties File (Step 2) as the value for the Database Resource in the GenRocket web platform. 


For example, JDBC is a common way to connect to a database. In the example below, resource.jdbc.directory has been added and is used to enter the database Connection Properties File path on the user's local machine.



Note: Additional information about configuring resources can be found in this knowledge base article: Organization Resources Overview.


Step 4: Download and Update my profile.prg

Any time the user changes the value of one or more resources, they will need to download their my profile.prg file and replace the old file on their local machine. 

These steps vary per operating system. To learn more, please see one of the following knowledge base articles: 


Step 5: Customize the EDI Standard Template at Project Level

If no changes are made within the EDI Project, a standard template will be generated for EDI test data. Customizations can be made in one of two ways: 

  • Standard Template at Project Level - These changes apply to all users and will appear in every generated EDI document/transaction set. To learn more, please see EDI Project Customization at Project Level.
  • Test Data Case or G-Case Level - These changes apply to an individual user and do not impact other users. Changes here should reflect individual test data requirements. Continue reading to learn more.


Step 6: Use the Self Service Platform for Individual Testing Requirements

Any changes that do not apply to all users should be configured within the Self Service Platform as G-Cases. Optionally, users can set up G-Rules to apply logic and G-Queries to query real data from a database, CSV file, or Excel file.

Note: See this article to learn more about EDI and the Self Service Platform: Self Service for EDI Overview.


Step 6a: Set up Test Data Cases (Recommended)

G-Cases speed up the process of creating Test Data Cases with many variations (Loop Counts) for different types of testing (Beta, Unit, Load, etc.). Accelerated G-Cases are available for these EDI documents/transaction sets: 834, 835, 837P, 837I, 820, 276, 277, 270, 271, and 278. Below are the accelerated G-Cases for an 837I document: 



Users can copy an accelerated G-Case or the entire G-Case Suite. Once copied, they can modify it to generate EDI documents/transaction sets for specific testing requirements. Additionally, users can create new G-Cases by completing the following steps: 

  1. Create a G-Case Suite
  2. Create One or More G-Case Categories
  3. Create One or More G-Cases per Category
  4. Add Domains to each G-Case and Set Loop Counts
  5. Select Rule Suites and Queries for the G-Case
  6. Download the G-Case Configuration File


The following knowledge base articles can be used to learn more about setting up and using Test Data Cases within the GenRocket web platform:


Step 6b: Set up Test Data Queries (Optional)

Sometimes, real data needs to be queried and blended with synthetic test data to meet specific testing goals. Test Data Queries or G-Queries enable the blending of synthetic test data with real data. Within GenRocket, you can query real data from a database or a CSV file. 


To set up a Test Data Query, you will need to do the following: 

  1. Set Parameters for the Query (This will vary depending on whether a database, CSV file, or Excel file is being queried)
  2. Enter the Query to be performed on the Database, CSV, or Excel file.
  3. Add Domain Attributes for Each Column in the Database, CSV, or Excel file.
  4. Add the G-Query to the G-Case


The following knowledge base articles can be used to learn more about setting up and using Test Data Queries within the GenRocket web platform: 


Step 6c: Set up Test Data Rules (Optional)

Test Data Rules or G-Rules allow you to apply business logic when generating your test data. To set up and use Test Data Rules, you will need to do the following: 

  1. Create a Test Data Rule Set
  2. Create Test Data Rules
  3. Add Conditions and Actions for Each Rule
  4. Add the G-Case Rule to the G-Case.


Test Data Rules can be used to set up and test business logic for data generated by Domains within a Project or Project Version. Each Test Data Rule contains one or more Conditions and Actions, which are applied during data generation.



The following knowledge base articles can be used to learn more about setting up and using Test Data Rules within the GenRocket web platform:

Step 7: Download G-Case Suite or G-Cases

If G-Cases will be used to customize the EDI document or transaction set based on testing requirements, the G-Case Suite or individual G-Cases will need to be downloaded to the user's local machine. 



Note: When a G-Rule Suite or G-Queries have been added to a G-Case, they will be automatically applied during test data generation. They do not have to be downloaded; only the G-Case Suite or individual G-Case needs to be downloaded.


Step 8: Download the EDI Configuration File

After your EDI Project has been configured appropriately, the user must download the EDI Configuration File from within the EDI Management Dashboard shown below. 


Click on the EDI Config button to download your EDI Configuration File for a selected EDI Project and Version.



Step 9: Download the Scenario Chain Set for the EDI Project

Next, you will need to download the Scenario Chain Set that is part of your EDI Project. Please note that this may take a few minutes to complete. 


This can also be done through the EDI Management Dashboard shown below. Click the Scenarios button to download your Scenario Chain Set for the selected EDI Project and Version.



Step 10: Run the Scenario Chain Set with a Test Data Case from the Command Line

The command line for running a Test Data Case is displayed at the bottom of the Test Data Cases Dashboard. This command line reflects the currently selected Test Data Case within a set. 



Important: If a Test Data Case is not needed for test data generation, users only need to run the Scenario Chain Set from the command line.


genrocket -r ScenarioChainSet.grs


Note: More information about running Test Data Cases with Scenario Chain Sets can be found in this knowledge base article: How to Download and Run a Test Data Case Set with a Scenario.


Useful Links

The following links can be used to learn more about getting started with GenRocket, EDI Projects, and Test Data Generation: 


Topic

Description

GenRocket Installation OverviewLearn more about GenRocket installation steps.
How do I make a connection to a MySQL database with the GenRocket Runtime?Learn more about connecting to a MySQL database.
Test Data Mapping Design PatternSee a Test Data Mapping Design Pattern for EDI. 
EDI Test Data Management OverviewLearn more about the EDI Test Data Management platform. 
EDI Management Dashboard OverviewLearn more about the EDI Management Dashboard. 
How to Customize an EDI Document OverviewLearn more about customizing EDI Documents/Transactions Sets. 
Self Service for EDI Overview
Learn more about customizing EDI Documents/Transaction Sets using the Self Service Platform. 
How Do I Generate My EDI Test Data?
Learn more about generating EDI test data.
How to Download and Run a Test Data Case Suite with a Scenario
Learn more about downloading and running Test Data Case Suite with a Scenario.


Useful Videos

The following solutions video is an excellent resource for getting started with GenRocket, the EDI Test Data Management Platform, Test Data Queries, Test Data Rules, and Test Data Cases: 


GenRocket Overview Video

The following solution video provides a quick introduction to GenRocket:


GenRocket EDI Test Data Management (TDM) Platform

The following solutions video provides a quick overview of the EDI TDM Platform: