Run and monitor transformation tests

A test run checks the transformation before you finalize it: it reads your source for the date you pick and prepares the output for review. Use the Validation step to run tests, watch them, read the test log and stop a run. The whole build, test and finalize flow is on Build, test and finalize a transformation; the review that follows a test is on Review test results and finalize a transformation.

Run a test

1. Open the transformation and go to Transformation > Validation.
2. Click Test Now. With no test yet, the step reads Test run required to complete transformation and explains: "Execute a test run to verify your transformation logic and preview the output before confirming."
3. In Test Transformation, pick the day on Select Date and the time under Select Time. The date starts on yesterday.
4. Set values under Run Parameters when the pattern is periodic; they apply to this test only. Transformation patterns and load settings describes them.
5. Click Test Now to start the run. While the request goes out the button reads Testing....
6. On success, "Test run started successfully" appears and the run shows up in the Latest Run card and the test log. If it cannot start, the dialog shows the reason above the buttons; when no reason comes back, it reads "Failed to start test run. Please try again."

• Until the target table is deployed, the step shows Target table not deployed instead of the test controls: "You can't run this transformation until its target table is deployed. Deploy the table first, then run a test." The table's name in the message is a link that opens the table; Deploy, run, truncate and monitor tables covers deploying it.
• While a test is running, you cannot start another: Test Now stays disabled until it finishes, and the step notes "A test run is currently in progress…".
• Saving a change to the query or the columns clears the last test, so the step asks for a test again and finalizing is blocked until a fresh test finishes.

Watch a running test

• The Latest Run card sits above the test log and summarises the newest run: its status badge, the Log ID, Rows and Duration tiles, then Start:, Snap Date: and User:, the person the run ran as.
• While the run is going, the step reloads the run data about once a second, so Rows, Duration and the status badge catch up on their own. A Running chip also shows beside the Test Log heading while any test is running.
• The card carries the run's controls: Show Error for a failed run and Abort while it is still going. Stopping a test and reading errors are described below.

Read the test log

• The test log lists the transformation's test runs, newest first: Log ID, Status, Rows, Error, User, Start, Finish, Duration and Snap Date. The toolbar searches the list, the columns sort and filter, and Refresh data reloads it by hand. If that reload fails, you see "Failed to refresh transformation runs".
• Double-click a run's row to open its details. A failed run's Error cell opens the full error stack.
• A run that is still going shows a stop control at the end of its row.
• The log shows 50 runs per page; the page size can be set to 20, 50, 100 or 500. A list with nothing to show reads "No test runs found".

Read a run's details and errors

• Transformation Run Details, opened by double-clicking a run, shows the run's status badge and ETL Log ID, then Processed Rows:, Pentaho ID:, User:, Start Date:, Finish Date:, Duration:, Posting Date: when the run carries one, and Error Information: when it failed. While the run is still going, Abort Run sits at the bottom.
• Show Error on the Latest Run card opens Transformation Error Details with the run's ETL Log ID and the full error stack, ready to read. Copy copies the stack and the button briefly reads Copied; Close closes the dialog.

Stop a running test

1. Start from any of these: Abort on the Latest Run card, the stop control at the end of the run's row in the test log, or Abort Run in the run's details.
2. In Abort Transformation Run, read: "Are you sure you want to abort this transformation run? This action cannot be undone." Confirm to stop the run.
3. "Test run aborted successfully" confirms, and the run reads Aborted. If the stop fails, an Error message names the reason; when no reason comes back, it reads "Failed to abort test run".

After a successful test

• A successful run reads Success. Until the transformation is finalized, the step replaces the test log with Confirm transformation after reviewing results and the line "Review the test run output to verify your transformation before confirming it for production." Click Show Results there to open the Test Results drawer.
• The drawer walks through Source Table, Target Output and Finalize. Review test results and finalize a transformation covers the review and the finalize step.
• Once the transformation is finalized, the test log returns, newest run first, and Test Now is no longer shown; you start production runs from the Execution tab.

Questions, answered

What does the Latest Run card show?

It summarises the newest test run: a status badge, the Log ID, Rows and Duration tiles, and Start:, Snap Date: and User: under them. Its controls open the error (Show Error), stop the run (Abort) or, once the transformation is finalized, open the results (Show Results).

Why is Test Now missing or disabled?

It is missing when the target table is not deployed yet: the step shows Target table not deployed instead, and the table's name opens the table so you can deploy it. It is also no longer shown once the transformation is finalized, because testing is done; you start production runs from the Execution tab. While a test is already executing, Test Now is disabled until that run finishes.

Does a test run change the target table?

No. A test run works on the date you pick and prepares what the query reads and what the transformation would write, so you can review it; your target table is not written. Production runs write the table, and you start them after finalizing.

How do I stop a test that is still running?

Click Abort on the Latest Run card, the stop control at the end of the run's row, or Abort Run in the run's details, then confirm in Abort Transformation Run. "Test run aborted successfully" confirms, and the run reads Aborted.

How do I open a test run's details?

Double-click its row in the test log. Transformation Run Details opens with the run's rows, times and user, plus Abort Run while it is still going; a failed run's Error cell opens the full stack.

What do the run statuses mean?

Running means the run is still executing, Success that it finished, Failed that it errored and Aborted that it was stopped. Any other value reads Unknown.

Does the Latest Run card update by itself?

Yes, while the run is going: the step reloads the run data about once a second, so Rows, Duration and the status badge catch up on their own. A finished run stops updating.

What happens when I click Show Error?

Transformation Error Details opens with the run's ETL Log ID and its full error stack. Use Copy to copy the stack (the button briefly reads Copied), and Close to close the dialog.

Why did the log turn into "Confirm transformation after reviewing results"?

The newest test finished successfully and the transformation is not finalized yet, so the step asks you to check the output before confirming it: "Review the test run output to verify your transformation before confirming it for production." Click Show Results to review the source and target rows and finalize; Review test results and finalize a transformation covers that step. Once the transformation is finalized, the test log returns.

Why do I need a new test after changing the query or columns?

Saving a change to the query or the columns clears the transformation's last test, so the step asks for a test again and finalizing is blocked until a fresh test finishes.

What is the difference between a test run and a production run?

A test run checks the transformation before you finalize it and never writes your target table; its history stays on the Validation step. Production runs write the target table and appear in the Run Log on the Execution tab, which never shows test runs.