Operations of a test execution

In the Data Processing Execution dialog box, select Execute as a test, and then specify the file name of the test result file. After you click the Run button in the Data Processing Execution dialog box, the number of detected errors is also displayed in the dialog box that displays the progress status.

Even if the input data contains some abnormal data, the data processing is executed to the end of the input data. During the test execution, the operation to the database (insert, update, delete) is not committed. If you want to commit the data, you need to execute the regular data processing.

The data processing of a test execution is executed in one-record units, and the individual fields are checked for errors. Basically in the test execution, a record is processed to the end of the record and then the next record is processed. If multiple error fields are detected in one record, the error count is increased per each error field, and the error information per each error field is output to the test result file. If multiple errors are detected in one field, the error count is increased by one, and only information about the error, which was detected at first, is output to the test result file.

A test execution is stopped if you click the Cancel button on the Progress screen, or the number of error fields exceeds 10,000.

= Remarks =

  • The data processing of a test execution is executed in a single thread.

  • If the custom error condition and test execution are used together, even if an error that meets the custom error condition occurs, the test execution will be executed continuously.

  • For test execution, data processing log is not generated in any of the following cases:

    • If the Cancel button was clicked in the Progress screen within the Execute Data Processing screen;

    • If the test execution finished normally.