-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added the Activity Registration required failure scenario to replayer test suite #1231
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've got some changes coming in another PR (not yet up, tackling other things first), but to follow those changes:
- no mixedCase files, use snake_case. both because it's a Go convention and because it consistently avoids case-(in)sensitive-filesystem issues.
- make sure you actually run these, apparently they're not run by our
Makefile
:| oops.
…his is an expected behaviour and test is included for documentation purposes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sounds good for now 👍
I've got a PR or two to come with some hopeful improvements for these, but let's get this merged in the meantime.
What changed?
Added a new workflow and a test case in the replayer test suite.
The new workflow demonstrates how failing to register a new activity throws a non deterministic error.
This reinforces the requirement of RegisterActivityWithOption option in the replayer.
Why?
Made these changes to remember that the replayer requires a new feature.
How did you test it?
tested locally.
Potential risks
NA