You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 18, 2021. It is now read-only.
While this is not wrong in that module, it is misleading and rather dangerous. This type is based on,and almost equal to the one I define in my blog post, but not quite. Compare to the Event type defined in Test.StateMachine.Lockstep.NAry:
This records the mock response, not the real one. This is critical: if this records the real response, and then the rest of my blog post is used as is, then the postcondition becomes trivial, comparing the real response to itself.
The text was updated successfully, but these errors were encountered:
I don't remember why I did it like I did (perhaps I misunderstood your code?), and I'm not actively using that code anymore today, so I guess maybe the right thing is to simply remove it?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Module
Test.StateMachine.Labelling
definesWhile this is not wrong in that module, it is misleading and rather dangerous. This type is based on,and almost equal to the one I define in my blog post, but not quite. Compare to the
Event
type defined inTest.StateMachine.Lockstep.NAry
:This records the mock response, not the real one. This is critical: if this records the real response, and then the rest of my blog post is used as is, then the
postcondition
becomes trivial, comparing the real response to itself.The text was updated successfully, but these errors were encountered: