With the help of the add-on module Test Case Manager, automated profile tests can be designed. (Unwanted) changes in the destination data of a profile, for example, because of optimizations and/or by a version change of Lobster_data, can be checked quickly and reported in the form of a report.

Procedure

There can be exactly one test case for a profile. The test case is determined by

1 to n test input files and
(optionally) another format check based on the contents Content of IU, Excel, FixRecord or CSV of the Response Route.

A test case can only be created for active profiles with the mapping enabled. Each test case must be recorded first. The result of this recording is the basis of comparison for subsequent test runs.

During recording, an internal XML file of the destination data is generated per test file (and a second one if there is a format check). The functions and macros used are analyzed and their return values are managed separately internally. They will then be included in the corresponding subsequent comparison test. The function now(), for example, returns a different result every time it is called and would always produce a deviation.

All mappings are treated like a mapping test, i.e. phase 4 is only simulated. Existing Response Routes are overlayed by the definition of the format check mentioned above.

If SQL (phase 4) is activated in the profile, an SQL log is generated.

If deviations have been determined, they are reported by email and are included as attachment (Excel file).