CtrlK
BlogDocsLog inGet started
Tessl Logo

engram-testing-coverage

TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

When to Use

Use this skill when:

  • Adding new behavior
  • Fixing a bug
  • Refactoring logic with branch complexity

TDD Loop

  1. Write a failing test for the target behavior.
  2. Implement the smallest code to pass.
  3. Refactor while keeping tests green.
  4. Add edge/error-path tests before closing.

Coverage Rules

  • Cover happy path + error paths + edge cases.
  • Prefer deterministic tests over flaky integration paths.
  • Add seams only when branches are impossible to trigger naturally.
  • Keep runtime behavior unchanged when adding seams.

Validation Commands

Run:

go test ./...
go test -cover ./...

Report package coverage and total coverage in the PR.

Repository
Gentleman-Programming/engram
Path

skills/testing-coverage/SKILL.md

Commit

763a6ba

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill