3 ms·
It is faster (same process, memory tables) but that’s my point: you can say you always need to test on your target database, which is true, but not needing to i
by acdha 6y ago
It is faster (same process, memory tables) but that’s my point: you can say you always need to test on your target database, which is true, but not needing to install things is a benefit, and that can matter when you’re doing integration tests with lots of data. I have seen plenty of projects where fast local SQLite + CI Postgres with lots of test data is reasonable.
- pydry 6y agoIt can suffice, but it will never be ideal. I had a project just a few weeks ago where somebody tried to do that and hit a brick wall nearly instantly because one table had an array column. SQLite instantly became useless. IME unrealistic tests bite much harder than slightly slower tests or needing to install the odd bit of software. Realism is pretty much the only thing that gives you confidence you'll actually catch some damn bugs...
- acdha 6y agoYou’ll note that I said the same thing. The point was just that the set of bugs people write includes both those which will affect any database and those which depend on certain configuration and behaviors. There are enough people who find it useful to do both that I’m comfortable saying any position which pretends they don’t exist is incomplete. As with the original author, the problem here is forgetting to add “On my projects” or “In my experience” rather than speaking in absolutes.