Cypress database handling - Rainer Hahnekamp

Cypress and the database or 'The elephant in the room' - Rainer Hahnekamp
We all know the problem. A test causes some changes in our database. These changes can break the following tests. Not the nicest thing to do.
Unfortunately, we can't just always mock the database as we can in Unit Tests. So we have to find other ways.
This talk is about various strategies for how to set up our tests so that they have the least possible effect on others.
Rainers Twitter: / rainerhahnekamp
Join our meetup community: www.meetup.com/de-DE/cypress-...
Discord: / discord
Twitter: / decypressusers

[@yuriivoina1261]

Thank you very much for such video !!

[@g.likestefani3155]

Very helpful thanks from France 🇫🇷

[@NeverCodeAlone]

Very good and thx for your passion!!

[@kolyokolev5652]

Very helpful video. Thank you for the pro level of explanation and work done here.

[@rawgov]

Great talk. To the point and offered some good strategies.
Now I need to find out the best strategy to create a branch for a Test API and run it locally before deploying changes to the production build. So that it is all part of the CI.

[@servandocerna5610]

Thanks very much for the explanation!

[@amarpreetsingh1882]

Very helpful explanation.

[@gonsfx1792]

Not helpful. If you want real e2e tests and test isolation, you have to reseed the database or start with a blank one for each individual test. If starting with a blank one is not a possibility due to the complexity of the required database setup, the only option you're left with is reseeding. This talk doesn't give any advice on how to do this in the most performant way.

[@ercancaglayan4594]

this is cypress, show it instead of explainnnnnnnnn