Repository navigation
feat(verify,debt): track test speed every phase, warn on slowdowns (#114) - #125
Merged
Merged
Conversation
) New tested script test-times.sh times the suite, records it in .planning/test-times.tsv, keeps the 10 slowest tests, and warns (never fails) on a >25% and >=5 s slowdown or any test over 10 s. verify uses it in 3.2; debt tests lists slow tests as debt items. Co-Authored-By: Claude Opus 5.5 <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
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.
Closes #114. Skills half: rshankras/claude-code-apple-skills#70.
In plain words
Tests written by agents tend to get slower phase after phase, and nobody notices until every build takes ages. Now
verifytimes the tests every phase and tells you in plain words when they got noticeably slower, naming the slowest ones. It never fails a phase for it.What changed
templates/_scripts/test-times.sh. Runs the test command, times it, and reads per-test times from both XCTest and Swift Testing output. Records date, phase, seconds and test count in.planning/test-times.tsv, and keeps the 10 slowest in.planning/test-slowest.tsv. Warns when the suite is over 25% and at least 5 s slower than last time (so 2 s → 3 s isn't news), or any test takes over 10 s. Exits with the test command's own result.verify3.2 runs the suite through it. A warning becomes one Low issue naming the likely cause (an app launch per UI test, copied tests, real network orsleep). It's shown in VERIFICATION.md and the review guide.debt testslists every test over 10 s as a debt item; DEBT.md gets a "Slow tests" line.testing/SKILL.md, pointed to fromtdd-featureandtest-generator.Tests
12 new script tests. Five planted bugs (no 5 s floor, threshold too high, exit code swallowed, the "Test run with…" total counted as a test, 10 s limit too high): each caught, then reverted. The tests also caught a real bug while I wrote them: XCTest times were read as 0.
🤖 Generated with Claude Code