# TRIP-test

> Write/run tests following project standards (deep test authoring)

- Skill: `pilastdigit/trip-test` (Agent Skill)
- Install (CLI): `npx skillmds@latest add pilastdigit/trip-test`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pilastdigit/trip-test/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: pilastdigit (https://skillmd.com/u/pilastdigit)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/pilastdigit/trip-test

---


# Testing Mode

You are now in **testing mode** for **[PROJECT_NAME]**.

This skill is the **deep test-authoring reference**: the `TRIP-2-implement` testing gate points here for heavy authoring work and full guidance. Invoke it standalone for test backfill or coverage work outside an implementation session.

## Prerequisites - Read First

Before testing, you MUST read:

1. @docs/ARCHI.md - Understand system architecture
2. @docs/4-unit-tests/TESTING.md - Testing guidelines

## Your Task

Test: $ARGUMENTS

---

## Testing Guidelines

### Scope

- Only run tests for relevant files that changed (not the whole project)
- Focus on the new feature/fix/refactor

### Commands

```bash
# [ADAPT_TO_PROJECT: Replace with actual test commands during Init]

# Run all tests
[TEST_COMMAND_ALL]

# Run specific test
[TEST_COMMAND_SPECIFIC]

# With coverage
[TEST_COMMAND_COVERAGE]
```

### Test Structure

[ADAPT_TO_PROJECT: Describe where tests are located and naming conventions during Init]

### Testing Priorities

<!-- [ADAPT_TO_PROJECT: Replace with project-specific testing priorities during Init] -->

**Unit Tests**:

- Core logic functions
- Utility functions
- Individual modules/components

**Integration Tests**:

- Module interactions
- External service integration
- End-to-end flows

**What to Test**:

- Happy path scenarios
- Error states and error handling
- Edge cases (null, empty, boundary values)
- Invalid inputs

---

## Hard-to-Test Code

Seam ladder, cheapest first: **exported pure helper → injectable client/adapter → module mock → integration/emulator test**. Take the first rung that works; refactor for a seam only if the refactor is smaller than the feature you're shipping — otherwise it's coverage debt. Before refactoring legacy code, pin it with characterization tests (assert current behavior as-is, then refactor safely).

Uncovered risky paths: one line each in `docs/4-unit-tests/COVERAGE-DEBT.md` (`path | why hard | escape plan`). Delete a ledger line in the same change that gives its path meaningful coverage.

---

## Post-Testing Summary

After completing tests, create a summary file:

**File**: `docs/4-unit-tests/wa_vx.y.z_test.md`
(a = project week, x.y.z = version)

**Content**:

```markdown
# Test Summary - Week a, V. x.y.z

## What Was Tested

[List of tested components/functions]

## Test Results

- Total tests: X
- Passed: X
- Failed: X
- Coverage: X%

## Key Findings

[Any issues discovered, edge cases found, etc.]

## Notes

[Additional context or recommendations]
```