Support

What is G-Delta? 

G-Delta automatically detects database schema changes in your environment and updates the test data project so that the generated test data reflects the latest database structure. Changes are detected through an automated check ("audit") and then synchronized through G-Repository with GenRocket Cloud to update the relevant Project Version components (i.e., Domains, Attributes, Scenarios, G-Cases, etc.). 

The automated check can be performed on a scheduled basis (frequently as 12 hours to a maximum of 24 hours) or requested ad hoc. G-Delta will deliver an Audit Report for detected changes, which can be viewed and  by an Org Admin or assigned G-Delta Admin. The Project Version associated with the delta will be refactored based on the accepted changes within the report.

To use G-Delta, customers must have a G-Repository server installed and active. G-Delta must also have an active connection to the database that is being audited.

IMPORTANT:  G-Delta does not detect the actual changes to the data values or missing data, etc. Only changes that will modify the database metadata will be detected. 

When Should G-Delta be Used?

• G-Delta should be used in green field and brown field application development and testing when you expect the database to change frequently due to ongoing/rapid development.  
  
  
• G-Delta can also be helpful for applications going through multiple releases and testing or ongoing changes. 

What Are the Benefits of Using G-Delta?

• An automated check on schema changes ensures that the testing team is aware of all the changes in the underlying database.
• Ensures that test data generated from GenRocket reflects the latest database schema.
• In conjunction with G-Repository, it automates the download of up-to-date test data project components such as Cases, Scenarios, Configuration Files, etc.

What Types of Changes are Detected? 

G-Delta detects the following types of changes:

• Addition/deletion of tables ("domains")
• Addition/deletion of columns ("attributes")
• Changes to the name of domains or attributes
• Changes in data types of an attribute (e.g., changing from num to alpha/num, etc.)
• Domain Relationship Changes (e.g., adding a new table alters the relationship, etc.)

How Does G-Delta Work? 

1. Assign the G-Delta Admin role to one or more users.
   • Assign to a minimum of one user. It is recommended to assign this role to two users. 
   • Org Admins can create G-Deltas and manage Audit Reports. They do not need the G-Delta Admin role.
   • You can assign the G-Delta Admin role to a general user or project creator to manage their deltas.
2. Install and run the G-Repository Server.
   • Required to check changes in the database schema and provide updates to GenRocket Cloud. 
   • G-Repository Server must be actively running for G-Delta to detect changes.
3. Import the database schema metadata into a Project Version. 
   • We highly recommend using XTS Wizard to import the database schema metadata.
   • You can use other methods, such as DDL, JSON, CSV, XSD, and Scratch Pad, as long as the Domain Relationships and Attribute Types are defined.
4. Create a G-Delta for a Project Version within the Project.
5. Wait for an Audit Report to be Available (or Request an Audit Report). 
   • Assigned G-Delta Admin(s) will receive an email notification. 
6. Modify, Accept, or Reject recommended actions for each audit item within the report.
7. Accept or Reject the Audit Report to initiate refactoring of the Project Version.

How to Access G-Delta for a Project

You can access G-Delta from the Projects pane or the Self-Serve Menu options.

Method 1: Click on the G-Delta icon within the Projects pane for the Project.

Method 2: Select G-Delta in the Self Serve Menu Options for a Project Version. 

Additional Information