Skip to content

Conversation

3vilhamster
Copy link
Contributor

What changed?
Added unit tests for DecisionTaskWithHistoryIterator inside Replayer.
I had to go with instanstiating private class, otherwise I need to build the whole history for replayer.

Why?
Improving code coverage.

How did you test it?

Potential risks

Release notes

Documentation Changes

}

@Test(expected = Error.class)
public void testGetHistoryFailure()
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a spin lock :( retryOptions does not have a backoff coefficient. So it tries around 100 times in 4 seconds until it gives up. Our tests are rather slow, but I'm unsure how this should be resolved.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've switched to usage of validateBuildWithDefaults since I think it should be used instead of manual build()

@3vilhamster 3vilhamster enabled auto-merge (squash) November 28, 2024 20:16
@3vilhamster 3vilhamster merged commit 0e1916e into cadence-workflow:master Nov 28, 2024
6 of 7 checks passed
@3vilhamster 3vilhamster deleted the replay-tests branch November 28, 2024 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants