Using Test Data Queries (G-Queries) with EDI Overview
Important: We recommend going through the Software Tester Intermediate Flight Plan first to become more familiar with setting up and using G-Queries within the GenRocket web platform.
This lesson provides an overview of how G-Queries can be used with G-Cases to query a Database or CSV File and blend those values with synthetic data within the generated EDI Document/Transaction Set.
Test Data Queries are a key part of GenRocket’s Self Service Test Data Portal. We organize all the Test Data Query functionality into a part of the GenRocket platform we call “G-Queries.”
What is a Test Data Query (or G-Query)?
A Test Data Query queries real data from a defined Database or CSV file and then blends it with synthetically generated test data when run with a Scenario, Scenario Chain, or Scenario Chain Set.
Six Types of Queries
GenRocket Test Data Queries provides six types of query options:
Query Before – Query columns from one or more database tables as a set of data that is buffered into memory.
Query Each – Query one row of columns, from one or more database tables, on each row iteration of test data generation.
CSV List – From a CSV file, pull rows of data having one or more columns into memory as a list of data.
CSV Index – From a CSV file, pull rows of data having one or more columns into memory and retrieve any row via its row index.
Mongo Before – Query columns from one or more database collections as a set of data that is buffered into memory. This option is the same as Query Before but explicitly designed for use with Mongo.
Mongo Each – Query one row of columns, from one or more database collections, on each row iteration of test data generation. This option is the same as Query Each but explicitly designed for use with Mongo.
How can they be used with EDI?
Users can set up G-Queries to query real data from a Database or CSV File. Columns within the Database/CSV File are mapped to a selected Domain (i.e., Segment/Loop) and Attribute (i.e., Element).
The generated EDI Document/Transaction Set will have the real data values for each Domain Attribute (i.e., Element) that was mapped in the G-Query.
For example, a G-Query can query a CSV File containing Claim or Service Line information.
Important: Using many Q-Queries will increase the time it takes to generate EDI data.
How to Access G-Queries from the EDI Management Dashboard
Step 1: Expand the Management Menu within the Menu Bar and select EDI Management.
Step 2: Select the EDI Project within the EDI Header Pane.
Step 3: Select the EDI Project Version within the EDI Versions Pane (if the EDI Project has multiple Project Versions).
Step 4: Click on the G-Queries button.
How to Access G-Queries from the Project Dashboard
Step 1: Select the EDI Project within the Projects Pane.
Step 2: Select the EDI Project Version within the Project Versions Pane (if the EDI Project has multiple Project Versions).
Step 3: Expand the Self Serve Menu Options drop-down menu and select G-Queries.
Step 4: Select the EDI View option within the drop-down menu at the top left of the G-Rules Management Dashboard.