4 ms·
If you're using an ORM, it can be an easy way to ensure that no vendor specific stuff sneaks in. Also, until recently it was difficult to run, e.g., SQL Server
by james-mcelwain 8y ago
If you're using an ORM, it can be an easy way to ensure that no vendor specific stuff sneaks in. Also, until recently it was difficult to run, e.g., SQL Server in Docker, so Postgres might be easier to test with. Agreed SQLite is a weird choice, but not all integration tests are robust enough to test characteristics of the underlying db, i.e. focus on business logic not performance.
- majewsky 8y agoI have several dozen tests that run in completely separate DBs. With SQLite, the test suite runs through in 1 second: $ time go test github.com/sapcc/limes/... | grep -v 'no test files' ok github.com/sapcc/limes 0.004s ok github.com/sapcc/limes/pkg/api 0.515s ok github.com/sapcc/limes/pkg/collector 0.449s ok github.com/sapcc/limes/pkg/core 0.006s I doubt that you can setup and tear down several dozen Postgreses in that time.