The QA Team uses QuerySurge to perform both Functional and Regression testing.

Functional Testing

• The QA team writes and executes Tests during the development cycle to give the development team quick feedback on each ETL build deployed during development.
• QuerySurge is used for rapid high-volume data testing during the development cycle – for whatever period and at whatever sample size makes sense for the project.
• Tests are run when each ETL leg completes, helping to pinpoint where defects appear in the code. QuerySurge’s execution API can be used to trigger execution automatically when each ETL leg completes, for 24x7 automated build/test execution.

Regression Testing

• The QA team executes a full regression test covering 100% of all ETL mappings prior to deployment of the ETL code to production. The team tests a large sample of the data from each source system. Test data sample sizes up to 100% (Full coverage) for each source system can be validated.
• QuerySurge generates reports that provide auditable records of official test cycles for organizations that require downstream audits of testing activities.

The ETL Team uses QuerySurge to perform Unit Testing.

Unit Testing

• The ETL team uses QuerySurge to build ‘Unit-test’ QueryPairs as ETL code is developed, for immediate testing as code is committed in the development environment.
• Developers build queries ‘on-the-fly’, execute them, and see immediate results from QuerySurge.
• Developers execute with relatively large Result sets to profile more data than would otherwise be feasible.
• Developers catch issues in their code quickly in the Unit test phase with QuerySurge, reducing remediation costs to the project.

The Analysts Team uses QuerySurge to verify that the tests meet specifications and to analyze data.

Data Analysis

• The Analyst Team examines the QueryPair assets to verify that the tests match the requirements in the mapping documents.
• The Analyst Team looks at preliminary QuerySurge Scenario runs to evaluate whether the queries tested a mapping correctly.
• Then, the Analyst Team verifies whether failures identified by QuerySurge are deemed true failures or whether they are acting according to specifications (i.e. type mismatches, row count difference, etc.)

The Operations team uses QuerySurge to perform Operational Monitoring of production ETL runs on a daily basis.

Operational Monitoring

• DevOps automates the execution of a library of SQL pairs on a regular daily cycle that start immediately after the ETL process ends, using QuerySurge’s execution API.
• Reports that monitor the ‘ETL health’ at a glance are triggered when the Tests complete and are distributed to stakeholders through QuerySurge automated email functionality.
• Issues are quickly identified and flagged.