base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct testing and dependency status in repository policies

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-07 18:28:19 +00:00
parent 7e67d1adfc
commit 8b6835b84b
3 changed files with 13 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/policy/testing.md
View File

@@ -2,7 +2,7 @@
**Base Policy Version:** 1.3
**Last Updated**: 2026-10-06
**Last Updated**: 2026-10-07
**Upstream Source:** [testing.md](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/testing.md)
@@ -44,8 +44,8 @@ Examples of appropriate seams include clocks, randomness, subprocesses, remote A
CommandKit is a library that defines CLI behavior. Its public consumer boundary
is the root facade, and backend integration belongs behind the internal adapter.
Select validation proportionate to the change. The developer guide owns concrete
commands as implementation lands; there is currently no Go suite. Prose-only
Select validation proportionate to the change. The [developer guide](../development.md)
owns concrete validation commands for the implemented Go suite. Prose-only
policy adoption requires document review, not new tests or checker code.
Tests in the default suite must be deterministic, offline, and independent of real credentials. They must not invoke paid APIs or depend on mutable external services. Tests that require live infrastructure must be explicitly opt-in and clearly separated from the default suite.