I have a few specs that run that seed the database...
# kotest
k
I have a few specs that run that seed the database with data, and then an afterSpec handler that truncates the db tables. For some reason, its truncating the tables halfway through running the next spec leaving my database in this awkward “should of been seeded but has no data” state. Any ideas?
a
to avoif this race condition, have you tried decorating your specs with
@DoNotParallelize
k
I did and it didn’t work. It turned out that I had some buggy cache in my spring context that wasnt restarted between tests.
👍🏼 1