docs: TESTING.md — integration-lane warning + test-discipline rule#390
Merged
docs: TESTING.md — integration-lane warning + test-discipline rule#390
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
Two docs-only commits in docs/TESTING.md.
6198542docs(docs: warn in TESTING.md that integration lane is disruptive; unsupported while using the machine #385): warn integration lane is disruptive6bdcc2fdocs(docs: TESTING.md should mandate test updates alongside feature/fix PRs #388): mandate test updates alongside feature/fix PRs#385 — §1 paragraph warning that integration lane spawns real iTerm2 windows/tabs, steals focus, can surface Quit iTerm? dialogs. Run on idle machine / VM / ssh. Cross-refs mitigations in flight (#379-#383).
#388 — new §1.1 "Testing discipline": every PR with code changes must include test delta (feature → tests, bug → regression test per #240, behaviour change → updated tests, integration change → baseline refresh). Mirrors CONTRACT's "amend in same commit" rule.
Closes #385, #388.