@jeremysmithco I think your rule of thumb is good 👍 My rule of thumb along these lines is don’t cause surprises. A rails dev would expect to be able to call that without introducing other objects (or whatever is triggering the exception)
@excid3 Ahh yes. Are they anything like ours where they lie about things? There's no way she ate a plate full of carrots and broccoli... even if they logged it on the app. I need evidence.
@jeremysmithco@strzibnyj Enter a complex enough code base and those mystery guests are likely to affect what you’re testing. Fixtures somewhat simulate the real application (users with real data). A clean DB for every test is good (quick) for testing but unrealistic.
@jeremysmithco 100% Building a good fixture set is a skill. Factories don’t help with these scenarios much either mind you (unless you happen to find the 1 test that sets up your exact scenario). Still lots of improvements to make on both sides
@jeremysmithco It actually messed up a lot of things for us like analytics events being sent from controllers. Might be an “us” issue though. We had to disable it entirely
@jnunemaker Yeah, I spent way too long trying to long press on the screen while sat in my car before thinking it would be something I’d do on my phone.
@_swanson that'll do it! We run a ~hourly cypress based "integration test" outside of our main app that checks the important flows for staging/production just in case we break something by accident. A bit overkill but has proved useful!