Skip to content
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

add custom retry configuration #30

Merged
merged 1 commit into from
Jun 19, 2024
Merged

add custom retry configuration #30

merged 1 commit into from
Jun 19, 2024

Conversation

jaypipes
Copy link
Member

Adds the ability to configure retry behaviour for any test spec, using either a constant interval or an exponential backoff.

In doing so, reworks the framework to have all calls to testing.T.Errorf() happen in the Scenario.Run() method, as well as have that method handle all retries. gdt-kube will need to be refactored to remove the retry behaviour implemented in that plugin.

Also, this finally fixes the way that failures are tested by using the strategy outlined in golang/go#39903.

Issue #26

Adds the ability to configure retry behaviour for any test spec, using
either a constant interval or an exponential backoff.

In doing so, reworks the framework to have all calls to
testing.T.Errorf() happen in the Scenario.Run() method, as well as have
that method handle all retries. gdt-kube will need to be refactored to
remove the retry behaviour implemented in that plugin.

Also, this finally fixes the way that failures are tested by using the
strategy outlined in golang/go#39903.

Issue gdt-dev#26

Signed-off-by: Jay Pipes <[email protected]>
@jaypipes jaypipes merged commit 0eff693 into gdt-dev:main Jun 19, 2024
11 checks passed
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.

1 participant