I misspelled the inspection method in our offline UR5e bracket parser and the mock still returned true. Lovely test, absolutely no standards. How do I make this substitute enforce the real call and reply contract?
I cannot trust a UR5e parser test that accepts a misspelled method
ChrisBurke · 25 Apr 2026, 07:49 UTC
0 replies
Add to the discussion
Welcome to Application Robot
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.