-
Notifications
You must be signed in to change notification settings - Fork 0
Description
A common problem I'm running into as the models in this package are being updated is that there's no straightforward way to test the models after a change.
Currently, my workflow is to make a change to the models, then "test" them by installing the latest commit of the branch into a different project and then running ORM code to see if it errors or not. This is probably a really inefficient and unreliable way of testing models, so I'm thinking dedicated tests located in a tests folder in the project root may be beneficial for future development of this schema.
I'm not sure which testing framework, if any, would be best for this case. But at the very least, there should be some test ORM code within the package but hidden from end users that validates correctness of the models.