ETL Validator has a Client-Server Architecture with a Repository database for storing test case metadata and a Workschema database for storing the test data.

The key components of ETL Validator are :

ETL Validator Client

The ETL Validator Client is a windows based application that provides the User Interface for creating Test Cases, Test Plans and managing their execution in the ETL Validator Server. ETL Validator Client also provides interface for administration of the solution.

ETL Validator ELV Server

The ETL Validator ELV Server is a J2EE application running in Tomcat used for executing of Test Cases and Test Plans. It has a built in ETL engine for extracting and loading test data from heterogeneous data sources. It also has a scheduler for automatic execution of Test Plans at specified times and a file watcher that checks for any new files arriving in the specified folder before kicking off Test Plans.

ETL Validator Repository

The ETL Validator Repository stores the metadata related to test cases, test plans, data source connections and users. It requires an Oracle or Postgresql database.

ETL Validator Work Schema

The ETL Validator Work Schema stores the test data, benchmark data and the data validation results. It requires an Oracle or Postgresql database.

ETL Validator Reports

ETL Validator Reports is a web-based interface for viewing Test Case and Test Plan run results. It allows you to download results in a PDF or Excel format. It is a Java-based application that can be deployed in Tomcat along with the ETL Validator Server.

ETL Validator Command Line

A jar file (dgcl.jar) for remotely invoking test plan and test case runs from the command line. Additionally, it provides a command interface for invoking test case from HP Application Lifecycle Manager (ALM) or from CI/CD tool such as Jenkins. More details about the available command line interface can be found on our support site here.


© Datagaps. All rights reserved.
Send feedback on this topic to Datagaps Support