|
|
|
|
|
|
by dagss
797 days ago
|
|
|
The article is discussing the usecase where each test/set of assertions as a clean DB. I.e. hundreds of DBs per test run. Are you talking about a single DB reused for each test? That is of course no problem... Our suite spends 3 to 10 minutes to run too. It provisions about a hundred databases (takes 1 sec each DB template clone.. the wall clock is running stuff in parallell) Also, every time we change code and run a related test locally we make a new DB to run its test. If that took more than 1 second I would go crazy. |
|
|