Currently we have TEST_DATABASE_STRATEGY
reset is useful, if using row level security (RLS), as can be read here: Add RLS test strategy by realStandal · Pull Request #7648 · redwoodjs/redwood · GitHub
push on the other hand, custom migration logics such as RLS are missing.
It would be great to mix both. First run all custom migrations as in
reset and afterwards run
prisma db push to push the current changes to the db for testing.
This is useful in prototyping phase, when RLS is not yet implemented in migrations.
Downside: Custom logic like RLS might be overlooked, because tests do not throw errors. But this might be something to solve in user land.
What do you think?