Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

0007 — Write core/instructions/testing.md #29

New Issue
Closed
opened 2026-06-28 17:10:20 +00:00 by Claude · 0 comments
Claude commented 2026-06-28 17:10:20 +00:00
Collaborator
Copy Link

What to build

Create the testing conventions instruction file at core/instructions/testing.md. Plain markdown, no frontmatter. The agent reads this file on demand when writing or running tests, as directed by the content index in providers/claude-code/CLAUDE.md.

The file establishes four key rules: prefer integration tests over mocks; automate everything automatable; test observable end-state, not implementation internals; no test is better than a wrong test.

Acceptance criteria

  • File exists at core/instructions/testing.md
  • Contains all four rules from the PRD Module 4 section
  • Plain markdown with no frontmatter or schema
  • In a new session, ask the agent to write a test requiring a mocked database — agent pushes back and proposes an integration test instead

Blocked by

  • 0004 — rewrite providers/claude-code/CLAUDE.md and retire global.md
## What to build Create the testing conventions instruction file at `core/instructions/testing.md`. Plain markdown, no frontmatter. The agent reads this file on demand when writing or running tests, as directed by the content index in `providers/claude-code/CLAUDE.md`. The file establishes four key rules: prefer integration tests over mocks; automate everything automatable; test observable end-state, not implementation internals; no test is better than a wrong test. ## Acceptance criteria - [ ] File exists at `core/instructions/testing.md` - [ ] Contains all four rules from the PRD Module 4 section - [ ] Plain markdown with no frontmatter or schema - [ ] In a new session, ask the agent to write a test requiring a mocked database — agent pushes back and proposes an integration test instead ## Blocked by - 0004 — rewrite providers/claude-code/CLAUDE.md and retire global.md
Claude added this to the Legacy / Triage milestone 2026-06-28 17:10:20 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone Legacy / Triage
Projects
Clear projects
No project
Assignees
Clear assignees
Claude renovate-bot Defame1297
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Defame1297/holocron#29
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?