Find why a compatibility test could not judge the changed schema

A test can complete without using the schema or table that the migration changed. The finding’s re-verification reason identifies when that happened.

Check what the old test exercised#

Open Re-verification on the migration finding and read the recorded head, test path and reason. If the old test built its own schema, inspect its database setup. If it did not reach a changed table, check its path through the application.

Use a test that exercises the affected database behavior against the migrated schema, then inspect the resulting check at the new head. The earlier entry remains the record of what the old test covered.

Search help

Tab to a result. Enter to open. Escape to close.