Make pgsql tests database agnostic and actual unit tests #264
Labels
area/testing
related to improving test coverage
kind/cleanup
no functional changes, only reorganization
kind/feature request
wishes for new functionality/docs
priority/medium
desired functionality
In the early stages of the project, most of the database tests were implementation agnostic and were running on each registered implementation. But it got removed after an internal discussion for a silly reason that I can't seem to remember. We should extract the tests from the pgsql package, make them database agnostic and move them to the database package, just like before.
Also, instead of using scenario based tests, we should definitely make them unit tests and use fixtures more often.
The text was updated successfully, but these errors were encountered: