[Bug?]: Flaky Testing with Prisma migrations failing about redwood HOT 5 CLOSED

The issue might be caused by the Jest VSCode extension. I have installed it for another repo and did not realize it affects my rw repo. Now after disabling it, tests run smoothly so far. Please do not invest more time right now. Going to let you know if it worked properly.

from redwood.

Hi @dennemark I'm talking to the team about next steps -- it would be great to have some profiling or metrics about what is going on in tests (maybe we turn on api/Prisma logging during test runs?) but have to think of a way of capturing this info.

I may also make sense for me to schedule a call with you to see more of your test structure and discuss ways to optimize.

One question, did you try: https://docs.redwoodjs.com/docs/testing#describescenario---a-performance-optimization

However, there are some situations where you as the developer may want additional control regarding when the database is setup and torn down - maybe to run your test suite faster.
The describeScenario function is utilized to run a sequence of multiple tests, with a single database setup and tear-down.

Also, we know of some large apps using Prisma Mock https://github.com/demonsters/prisma-mock and don't use scenarios but rather https://www.prisma.io/docs/orm/prisma-client/testing/unit-testing (or a custom implementation of it).

Again, happy to discuss further.

FYI - When scenarios were first introduced in pre RW v1, these Prisma mocking tools didn't exist.

from redwood.

Hi,
Those are great recommendations! Not sure if mocking prisma will help with RLS, but i could try.

I think I will also try to go back to an older working branch and see how different prisma/rw versions affect it. Should have tried this before...
Lets try to reduce the possible reasons, then I would be up for a call :)

Best!

from redwood.

after disabling it, tests run smoothly so far

Glad to hear. Do reopen if see any other issues.

from redwood.

Unfortunately still happening :/
I cannot reopen it.
Argh... somehow the extension enabled itself again...
Had to disable and restart vscode. lets see...

from redwood.