For the test data I recommend to have them in the database. Clever sovetuiu you in the face new test date know not what they do. The face is the slow (wait for the item, wait for this) and most risky (item does not exist in time and test collapsed). I recommend to use backend - API or something (look here
). Otherwise it will happen, here's the problem: test 1 will be generated across the face of the test date for 5 seconds and everything will be OK, and then when these tests will be 1000, the generation of test dates will take 83 minutes (huh?).
In General, if you have Docker is, what's stopping you in the way a cast DB to fill?