This repository was archived by the owner on Jun 3, 2026. It is now read-only.
docs: add chaos testing doc and example script#836
Open
ybdarrenwang wants to merge 6 commits into
Open
Conversation
7 tasks
f9573e6 to
c4525e8
Compare
c4525e8 to
e9877bc
Compare
7 tasks
dc71cac to
a13deef
Compare
poshinchen
reviewed
Jun 2, 2026
dfb621c to
5acf867
Compare
Contributor
|
This repository has been merged into the strands-agents/harness-sdk monorepo and will be archived shortly. All new development happens there. If this PR is still relevant, please recreate it against the monorepo. The code now lives under Apologies for the disruption, and thank you for contributing! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds documentation and example for the chaos testing module in Strands Evals.
The example demonstrates:
GoalSuccessRateEvaluatorand how to evaluate agent resilience with 3 new chaos evaluators (FailureCommunicationEvaluator,PartialCompletionEvaluator,RecoveryStrategyEvaluator)dict[str, dict[str, list[ChaosEffect]]]) for readable failure conditions (e.g.,"search_timeout","total_chaos")ChaosCase.expand(cases, effect_maps)to generate the Cartesian product of test cases × failure conditions with optional baselineChaosExperimentwithChaosPluginfor transparent fault injectionThe example uses
ToolSimulatorfor reproducible tool responses and covers pre-hook effects (tool call failures), post-hook effects (response corruption), and compound multi-tool chaos.Related Issues
#114
Type of Change
Checklist
npm run devBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.