Our offline UR5e fixture check accepts every input combination. Fake returns true everywhere. How do I make the application show carrier present but insert identity missing, without pretending I've simulated the fixture?
Replying to BrunoBrown0887
Give the application boundary explicit recorded cases for carrier present with identified insert, missing identity and conflicting identity, using the real interface contract. Assert the displayed fixture state and reason for each. Keep the separate installed confirmation checks with the maintainer; the fake cannot establish how the actual fixture is detected.
12 points