I removed the fixture-status call from our offline FR10 application and the test still passed. The mock returns true for anything it is asked, and the test only checks that the screen opens. What should the maintainer make this substitute complain about first?
Always-true mock covering a missing fixture-status call
NathanAbbott0025 · 5 Jan 2026, 21:42 UTC
1 reply
Replying to NathanAbbott0025
The missing required call, then wrong method names and arguments. Make it return the documented response shapes for your supported interface, including failures. A happy window isn't much of a parser test.
22pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .