CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/test-driven-development

Master Test-Driven Development with deterministic red-green-refactor workflows, test-first feature delivery, bug reproduction through failing tests, behavior-focused assertions, and refactoring safety; use when implementing new functions, changing APIs, fixing regressions, or restructuring code under test.

Review — 100%

Does it follow best practices?

Evaluation — 86%

↑ 1.05x

Agent success when using this tile

Validation — 11 / 11 Passed

Validation for skill structure

Overview
Skills
Evals
Files

org-file-structure.mdreferences/

title:
Follow Consistent Test File Structure
impact:
MEDIUM
impactDescription:
reduces time finding tests
tags:
org, file-structure, conventions, naming

Follow Consistent Test File Structure

Establish and follow a consistent pattern for test file location and naming. Developers should instantly know where to find tests for any code.

Incorrect (inconsistent structure):

src/
  services/
    userService.ts
    tests/
      userService.spec.ts
  models/
    user.ts
tests/
  models/
    user.test.ts
spec/
  integration/
    user_tests.js
__tests__/
  userStuff.ts

Correct (consistent co-located tests):

src/
  services/
    userService.ts
    userService.test.ts        # Unit tests next to source
  models/
    user.ts
    user.test.ts
  components/
    UserProfile.tsx
    UserProfile.test.tsx
tests/
  integration/                  # Integration tests separate
    user-registration.test.ts
    checkout-flow.test.ts
  e2e/                         # E2E tests separate
    user-journey.test.ts

Alternative (mirror structure):

src/
  services/
    userService.ts
  models/
    user.ts
tests/
  unit/
    services/
      userService.test.ts      # Mirrors src/ structure
    models/
      user.test.ts
  integration/
    user-registration.test.ts

Naming conventions:

  • *.test.ts or *.spec.ts - pick one, use consistently
  • Match source file name: userService.ts → userService.test.ts
  • Use descriptive integration test names: checkout-flow.test.ts

Reference: Jest Configuration - testMatch

Install with Tessl CLI

npx tessl i pantheon-ai/test-driven-development

references

assert-custom-matchers.md

assert-error-messages.md

assert-no-assertions-antipattern.md

assert-snapshot-testing.md

assert-specific-assertions.md

cycle-maintain-test-list.md

cycle-minimal-code-to-pass.md

cycle-refactor-after-green.md

cycle-small-increments.md

cycle-verify-test-fails-first.md

cycle-write-test-first.md

data-avoid-mystery-guests.md

data-builder-pattern.md

data-minimal-setup.md

data-unique-identifiers.md

data-use-factories.md

design-aaa-pattern.md

design-avoid-logic-in-tests.md

design-descriptive-test-names.md

design-one-assertion-per-test.md

design-test-behavior-not-implementation.md

design-test-edge-cases.md

isolate-deterministic-tests.md

isolate-mock-external-dependencies.md

isolate-no-shared-state.md

isolate-prefer-stubs-over-mocks.md

isolate-use-dependency-injection.md

org-file-structure.md

org-group-by-behavior.md

org-parameterized-tests.md

org-setup-teardown.md

org-test-utilities.md

perf-avoid-network-calls.md

perf-avoid-sleep.md

perf-fast-unit-tests.md

perf-fix-flaky-tests.md

perf-parallelize-tests.md

strat-coverage-targets.md

strat-e2e-critical-paths.md

strat-integration-boundaries.md

strat-mutation-testing.md

strat-test-pyramid.md

SKILL.md

tile.json