ETL Validator - FAQ

Yes. ETL Validator supports comparison of data from multiple source and target data sources in a single test case. It provides a visual test case builder for defining multiple data sources and validations for comparing them. 

ETL Validator provides a command line interface for invoking test plans and test cases remotely. This can be used to automatically execute tests as soon as the ETL process has completed. In addition, ETL Validator sends email notifications of the results from the test runs. 

Yes. Test Plans can be scheduled and email notifications will be sent automatically once the tests have been executed.

Yes. ETL Validator validator provides a web based reports for test plan and test case run results. These results can be downloaded into PDF and Excel spreadsheets so that they can distributes to other users. 

Often organizations receive flat files from external sources that need to be tested for data quality. File Watcher is part of ETL Validator that automatically detects new files coming into a folder and automatically kicks off a test plan. Users can get notification of the data quality tests as soon as the tests are completed. 

No problem. We will be happy to work with you to add support for the data source that you are interested in testing as long as it is our roadmap. We work in an agile manner to quickly add support for new data sources. 

Yes. You can download ETL Validator and try it out for 30 days. We will provide full support during this period for your POC. 

ETL Validator stores the test case metadata in repository database. The test data extracted from the data sources is stored in a workschema. ETL Validator currently supports Oracle 11g, Oracle 12c database or PostgreSQL 9.3.7 as the repository and workschema. ETL Validator Complete comes with an embedded postgreSQL repository and workschema.

1. ETL Validator Client: Windows based client for defining and executing tests
2. ETL Validator Server: J2EE server that typically runs in Tomcat 7 or later and JDK 1.7 or later. It can be deployed in a windows or unix environments.
3. Repository / Workschema: Oracle 11g or PostgreSQL 9.3.7 database
4. Web Reporting: Runs in a J2EE container such as Tomcat 7

1. Windows Machine
2. Java 7 or later