1. DB Best Documentation
  2. Error handling

Error handling

Test Organizer provides wide opportunities for errors handling — it’s important that both the Source and Target databases perform the same way, including errors. For expected errors, users can override syntax differences for similar errors by enabling the Compare error messages option. For not expected errors, users can pass them by adding custom error mapping rules.

Expected errors

The expected errors list includes errors defined within the Mapping rules to classify them as expected behavior.

Expected error

Figure 1. Similar expected error messages

To enable Error comparison, go to the Main Menu at the upper left corner of the screen, choose Project Settings > Test Organizer and check the Show the “Advanced compare options” tab option.

Advanced error options

Figure 2. Enabling Advanced compare options

Then, return to the main Test Organizer field and click on the Advanced compare options tab. Scroll down to the bottom of the tab, check Override parent options and Compare error messages and click Save.

Compare error messages

Figure 3. Enabling error comparison

After running the test, the expected error will be added to the exception and will have the “passed” status.

Expected error exception

Figure 4. Expected error added to exception

Not expected errors

The expected errors list includes errors whose scenarios are not included in the Mapping rules.

Not expected error message

Figure 5. Not expected error message

To enable custom matching, enable the Compare error messages option as in Figure 3. Then, go to Mapping > Error mapping rules and click Add.

Copy the error messages for both the Source and Target databases from the Results tab in the Test Organizer module and paste them in the corresponding fields of the Create error mapping rule menu, then click Save.

Create error mapping rule

Figure 6. Adding custom mapping rules

After running the test, the previously classified not expected error will be added to the exception and will have the passed status.

Not expected exception

Figure 7. Not expected error added to exception

Didn’t find the answer?

You can report problems, ask questions or share ideas for improvements on our email [email protected].