docs(test): require production-reachable unit tests - #2221
Merged
Conversation
Add explicit production reachability, test-helper scope, and counterfactual self-review requirements so realistic-looking test-only harnesses are not mistaken for behavioral coverage.
Binary Size Analysis (Agent Data Plane)Baseline: f90357b · Comparison: 11a3ac3 · diff ✅ Binary size difference within thresholdChanges by Module
Detailed Symbol Changes |
thieman
marked this pull request as ready for review
July 28, 2026 17:29
tobz
approved these changes
Jul 28, 2026
There was a problem hiding this comment.
More details
The PR adds documentation-only review guidance requiring tests to reach production behavior and survive a counterfactual mutation. The wording is consistent with the surrounding testing taxonomy and introduces no runtime behavior or clear diff-only hazard; documentation lint could not be completed because Vale is unavailable.
🤖 Datadog Autotest · Commit 11a3ac3 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
dd-octo-sts Bot
pushed a commit
that referenced
this pull request
Jul 28, 2026
Had the clanker try to self-remediate based on this discussion around some useless tests #2185 (comment) ## Summary - Require unit tests to exercise a production behavior or branch. - Prohibit tests whose sole subject is a test-only helper. - Add a counterfactual self-review check based on mutating or removing the claimed production behavior. ## Motivation A review of test-only networking helpers in #2185 showed that realistic setup and strong-looking assertions can still provide no production coverage. These rules make production reachability and mutation sensitivity explicit review requirements. ## Test plan - `make check-docs` - Repository pre-commit checks 151ad17
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
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.
Had the clanker try to self-remediate based on this discussion around some useless tests #2185 (comment)
Summary
Motivation
A review of test-only networking helpers in #2185 showed that realistic setup and strong-looking assertions can still provide no production coverage. These rules make production reachability and mutation sensitivity explicit review requirements.
Test plan
make check-docs