Skip to content

Add basic connection interruption tests #3292

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

uglide
Copy link
Collaborator

@uglide uglide commented May 13, 2025

  • Use reactor-netty-http client to interact with the Fault Injector
  • Test command execution and PubSub with dmc_restart, network_failure failures injected

uglide added 2 commits May 13, 2025 16:43
- Use reactor-netty-http client to interact
with Fault Injector
- Test command execution and PubSub with
dmc_restart, network_failure failures injected
Copy link
Collaborator

@kiryazovi-redis kiryazovi-redis left a comment

Choose a reason for hiding this comment

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

Good sample tests
Will prove invaluable as a starting template to further testing with fault injector
not an approver myself, though.

@tishun tishun added this to the Async milestone May 28, 2025
Copy link
Collaborator

@tishun tishun left a comment

Choose a reason for hiding this comment

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

I like it a lot.

My major question is - when / how do we run these.

Comment on lines +62 to +64
@ParameterizedTest
@ValueSource(strings = { "dmc_restart", "network_failure" })
public void testWithReactiveCommands(String triggerAction) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

I was wondering, since this is a scenario, if we would not benefit to have some more verbose way to describe exactly what we are testing. E.g.

https://junit.org/junit5/docs/current/user-guide/#writing-tests-display-names

@tishun tishun added the type: task A general task label Jun 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants