Introduction
MettleCI provides a comprehensive and sophisticated automated Unit Testing capability. The focus of MettleCI Unit Testing is create and publish, to Git, a set of artefacts (test specifications and associated test data) that embody a definition of (used to demonstrate) your job's correct functional behaviour. These artefacts can be propagated to downstream environments where they can be used to verify your job's consistent behaviour on DataStage platforms which may not have the same configuration, connectivity, or even DataStage version as the project in which the original job was developed.
The Unit being tested by MettleCI's Unit Test capability is an individual DataStage job. Unit testing is not intended to replace performance testing, nor does it support connecting to source or target databases to validate SQL queries. Broader-scoped testing activities (typically involving database interaction) is the role of MettleCi's End-to-End tests which are created, managed, and executed separately to Unit Tests.
Creating an Automated Unit Test
This animation describes the steps MettleCI goes through to create your Unit Test:
See how this is done from the MettleCI workbench here.
Capturing Unit Test Data
(Interception Description Here)
(Interception animation here)
See how this is done from the MettleCI workbench here.
Executing an Automated Unit Test
(Execution description here)
(Execution animation here)
See how this is done from the MettleCI workbench here.