chore: use dry run/mocks for fips tests#2100
Merged
ava-silver merged 3 commits intomasterfrom Feb 12, 2026
Merged
Conversation
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🔗 Commit SHA: e78cd09 | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
duncanista
approved these changes
Feb 12, 2026
Merged
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What and why?
This PR adds automatic detection of
--dry-runsupport for commands in the CLI test suite. This prevents real API calls during tests and makes the test suite more robust.Added because I was seeing flaky tests, and I think this should fix it
How?
supportsDryRunhelper function that checks if a command class supports the--dry-runoption--dry-runto commands that support it--dry-runflags from therequiredOptionsobject, as they're now added dynamicallyReview checklist