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 · 2026年1月5日 21:42 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
1 条回复
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.
22分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .