mirror of
https://github.com/penpot/penpot.git
synced 2026-09-17 09:26:14 +00:00
fbfef42145
.agents is the shared home that opencode, Claude Code (through the .claude/skills symlink) and Codex all read, so the skills and the saved plans now live there instead of .opencode: - .opencode/skills moved to .agents/skills (24 files, no content changes). - .opencode/plans moved to .agents/plans; the .gitignore entry follows, so plans stay untracked. - .claude/skills symlink retargeted to ../.agents/skills. - planner, make-a-plan and review-plan updated to the new plans path; new .agents/README.md documents every skill with when-to-use examples and links to each SKILL.md. - workflow/creating-issues memory: create-issue path updated. opencode discovers .agents/skills natively, so .opencode needs no reciprocal link. AI-assisted-by: omen-alpha
59 lines
1.9 KiB
Markdown
59 lines
1.9 KiB
Markdown
---
|
|
name: testing
|
|
description: Enforce TDD workflow and testing best practices for Penpot. Use when implementing features, fixing bugs, or modifying behavior. Reads testing memory for full guidance.
|
|
---
|
|
|
|
# Testing Skill
|
|
|
|
Enforces test-driven development and Penpot testing conventions.
|
|
|
|
## When to Use
|
|
|
|
- Implementing new logic or behavior
|
|
- Fixing any bug (reproduction test required)
|
|
- Modifying existing functionality
|
|
- Adding edge case handling
|
|
|
|
**Skip:** Pure configuration changes, documentation updates, or static content with no behavioral impact.
|
|
|
|
## Workflow
|
|
|
|
Follow TDD (Red → Green → Refactor) whenever practical:
|
|
|
|
1. **RED** — Write a failing test first
|
|
2. **GREEN** — Write minimal code to pass
|
|
3. **REFACTOR** — Clean up while tests stay green
|
|
|
|
For bug fixes, use the Prove-It Pattern: write a test that reproduces the bug, confirm it fails, implement the fix, confirm it passes.
|
|
|
|
## Required Reading
|
|
|
|
Before writing any test, read:
|
|
|
|
1. `.serena/memories/testing.md` — cross-cutting testing principles, TDD workflow, anti-patterns, execution discipline
|
|
2. Module-specific testing memory for the affected module:
|
|
- `mem:common/testing` — CLJC unit tests
|
|
- `mem:frontend/testing` — CLJS unit tests, Playwright E2E
|
|
- `mem:backend/testing` — JVM clojure.test conventions
|
|
- `mem:exporter/testing` — exporter unit tests
|
|
|
|
## Key Rules
|
|
|
|
- Every behavior change needs a test
|
|
- Test state, not interactions
|
|
- DAMP over DRY — tests are specifications; duplication is OK if each test is self-contained and readable
|
|
- Prefer Real > Fake > Stub > Mock
|
|
- Arrange-Act-Assert structure
|
|
- One assertion per concept
|
|
- Never pipe test output to filters — redirect to file first
|
|
- Register new test files in the module's runner/entrypoint
|
|
|
|
## Verification
|
|
|
|
After completing implementation:
|
|
|
|
- [ ] Every new behavior has a test
|
|
- [ ] All tests pass for touched modules
|
|
- [ ] Bug fixes include a reproduction test
|
|
- [ ] Lint/formatter passes
|