Why You Need to Call Fixtures, Not Detect Changes?

We spent two or three days just writing the same test in multiple ways. And f wou know exactly what every single line of code did. Oa, this is when why you need to call fixtures, not detect changes. And this is why you're calling flushyes, oint cause there'soin of that. And also not calling am fixures. Ogt to detect changes in your each because that actually then creates your component. For us, that meant agy cred was potentially being created outside of your facain zone. So it was really good to just work through that code and move things around between before each and into the test body.