Skip to content

Conversation

@krototype
Copy link
Contributor

Summary

A piece of middleware that enables developers to inject server failures that are difficult to trigger. The goal of this Chaos Handler is to allow a developer to test their application code with random errors injected into their application so that they can see whether the application handles server-generated failures. Additionally, a developer can explicitly control the generated failures to assist with reproducing the failure and aid in fixing the application behavior under failure conditions.

Motivation

Provide a configurable testing handler component that, by default, generates random error responses, and can be configured to generate tester specified errors.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • I have read the CONTRIBUTING document.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Copy link
Contributor

@muthurathinam muthurathinam left a comment

Choose a reason for hiding this comment

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

Approving as its a squashed PR of #227

@krototype krototype merged commit f37b583 into dev Dec 12, 2019
@nikithauc nikithauc deleted the abhsriva/ChaosHandler branch September 2, 2020 23:58
@nikithauc nikithauc added this to the Next milestone Oct 5, 2020
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.

4 participants