undefined | Better HN

0 pointsflakes2y ago0 comments

I do this a lot for Postgres testing. In my setup, I create a single database for the entire test run. Each test creates its own schema in that database and applies the latest table definitions.

With this setup, I only eat the container creation once, while allowing every test to operate in isolation from one another, be parallelized, and test against a real database.

I do a similar trick for S3 containers by applying a unique guid prefix to the buckets in each test.

0 comments

hnben2y ago

doesn't it take a lot of time to create the schema and populate it with enough data to get going?

flakesOP2y ago

It depends on what you’re testing. Applying the schema is pretty fast (30-40ms), compared to the container creation (1-2 seconds). If you need a lot of test data it would take time, but most of the time Im only applying enough rows to hit my test conditions. For crud apps I usually orchestrate the test setup using the public APIs of my application against the fresh instance.

j / k navigate · click thread line to collapse

0 comments

hnben2y ago

doesn't it take a lot of time to create the schema and populate it with enough data to get going?

flakesOP2y ago

j / k navigate · click thread line to collapse