Debugging and Testing

Errors in the plan are shown in the Properties panel as the plan is constructed, as shown in the following image.

Selecting an individual step shows only the warnings and errors for that step. Double-clicking on an error in the Properties panel opens the step properties dialog to the field which contains the error. Individual steps can also be debugged along the way by clicking the Debug button in the toolbar, when a step is selected, or by right-clicking on a step and selecting Debug, as shown in the following image.

It is possible to test a transformation plan without running the entire project. A folder called tests has been provided in the Files node, which is intended to store plans used for testing purposes.

Procedure: How to Test a Transformation Plan

To test a transformation plan:

Create a new MDS plan file inside the tests folder by right-clicking the folder context menu and selecting New and then MDS Plan.
Locate the .comp file in the Files/trans folder that corresponds to the transformation you wish to test (for example, Address_clean.comp for the Address_clean transformation), and drag this file onto the canvas of the newly created plan, as shown below.

This creates a component step with input and output endpoints.
To send to and receive data from this component, connect an input step (such as Text File Reader or JDBC Reader) to the input of the Component step, and an output step (Text File Writer or JDBC Writer) to its output.

This allows test data to be sent to and received from the transformation.
To run the plan, click on the Run button on the toolbar or right-click on the canvas and select Run, as shown in the following image.

When a plan is being run, its progress can be monitored in the Console window below the PlanEditor, as shown in the following image.