This bug was a compound result of several different issues.
Existing API integration test produce a false positive since getVersion() property accessor never matches the condition (and thus skipping the assertion). Before it was matching MigrationVersion with String.
Once the match has been fixed, existing assertions were throwing errors since recent commits had updated some of the assertion check values (e.g. column values), and create or drop tables had been introduced.
Pull Request (PR) Checklist
Documentation
[x] Documentation in README.md or Wiki updated
Code Review
[x] Self code review -- take another pass through the changes yourself
[x] Completed all relevant TODOs, or call them out in the PR comments
Summary
Fixes issue #30
This bug was a compound result of several different issues.
getVersion()property accessor never matches the condition (and thus skipping the assertion). Before it was matchingMigrationVersionwithString.Pull Request (PR) Checklist
Documentation
README.mdor Wiki updatedCode Review
TODOs, or call them out in the PR commentsTests