Migration Platform
Error mapping rules
The Error mapping rules tab allows for handling errors and making sure they perform the same way in both the source and target databases in the Test Organizer module. The default error list is made by our DBAs, however, the list can be modified by adding or removing new and existing rules. The list contains the most common error scenarios for each pair of source and target databases.
The error description shows the error codes and message differences between the source and target databases in relation to their syntax.
Figure 1. Default error mapping rules
The most common usage scenario is when tests with the error status need to be passed. You can see some of the objects having the error status in Test Suite of the Test Organizer module.
Figure 2. Test resulted in error
To make the test pass, you should enable the Compare error messages option. For that measure, select the tested object, click on the Advanced compare options tab. Then, scroll down to the bottom of the menu and check the Override parent options and Compare error messages options and press Save.
Figure 3. Error messages comparison enabled
After running the test, Migration Platform will automatically pass tests that match the default error mapping rules for both the source and target databases. If the test result still shows the error status, this means that the error scenario isn’t included in the default error mapping list and you need to add the error mapping rule manually.
To do that, copy the error codes and messages for both the source and databases, head over to the Mapping module, open the Error mapping rules tab, and press Add. In the opened window, paste the copied error codes and messages in the corresponding fields and press Save. It is sufficient to enter either error codes or messages.
Figure 4. Adding a new error mapping rule
Then, return to the Test Organizer module and run the test for the object that previously had the error status.
Figure 5. The passed test
As displayed above, the test passed successfully.
Didn’t find the answer?
You can report problems, ask questions or share ideas for improvements on our email [email protected].