I cannot trust a UR5e parser test that accepts a misspelled method

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?