I run a service business·I build them

AI-Assisted Testing & Tools

Building a Testing Culture

Technical skills alone are not enough — sustainable testing requires team norms, code review standards, and visible ROI.

Tests Require Culture, Not Just Skill

You can teach a team every testing pattern in this pillar. Tests still won't happen unless the team is committed to them.

Technical skills are necessary but not sufficient. A testing culture is built on norms, expectations, visibility, and demonstrated value.

Starting from Zero

If your codebase has no tests, retrofitting everything is impractical and discouraging. Start with three rules:

  1. Going forward: New features must include tests. No exceptions.
  2. Bug fixes: Before fixing a bug, write a failing test that reproduces it. Fix the bug; the test passes.
  3. Triage by risk: Identify the 10 most critical, highest-risk code paths (auth, payments, data mutations) and test those first.

The Boy Scout Rule: leave the code more tested than you found it.

Code Review Standards for Tests

Tests should be reviewed with the same rigor as production code. A culture where PRs without tests are blocked rapidly normalizes testing.

Questions to ask in review:

  • Does this PR include tests for the new behavior?
  • Are the test assertions meaningful (not just "doesn't throw")?
  • Are edge cases covered?
  • Do the test names clearly describe what is being tested?
  • Would a bug actually cause these tests to fail?

Tests as Documentation

Well-named tests serve as living documentation. Describe behavior, not implementation:

  • Bad: "calls db.users.findOne with correct params"
  • Good: "returns the user profile when authenticated"

Testing in the AI Era: The Winning Pattern

  1. Human writes the spec
  2. AI generates implementation
  3. AI generates tests from spec
  4. Human reviews and augments tests
  5. CI runs tests on every push

Key Takeaways

  • Start from zero with three rules: test new features, test bug fixes first, prioritize critical paths
  • Block PRs without tests — this creates cultural accountability faster than any other practice
  • Test names should describe behavior, not implementation
  • Make ROI visible: track bugs caught by tests, flaky test count, CI execution time
  • The AI-era winning pattern: human spec → AI implementation → AI test draft → human review → CI enforcement

Example

typescript
// Testing standards document (inline as test file pattern)

/**
 * TESTING STANDARDS — applies to all tests in this codebase
 *
 * Required for every PR:
 * - New business logic: unit tests
 * - New API routes: integration tests for all HTTP status codes
 * - New user flows: E2E test for the happy path
 * - Bug fixes: regression test that reproduces the bug
 *
 * Test naming convention:
 * it('[action/event] [expected result]', ...)
 * Example: it('returns 401 when token has expired', ...)
 *
 * Coverage targets:
 * - Auth and payments: 95%+
 * - API routes: 85%+
 * - UI components: 70%+
 *
 * PR reviewers must verify:
 * - Test assertions are specific and meaningful
 * - Error paths are tested, not just happy paths
 * - No new flaky tests are introduced
 */

// Example of standards applied:
describe('PaymentService.charge', () => {
  it('returns charge ID on successful payment', async () => { /* ... */ });
  it('throws InsufficientFundsError when card is declined', async () => { /* ... */ });
  it('does not expose full card number in error messages', async () => { /* ... */ });
  it('creates an audit log entry for every charge attempt', async () => { /* ... */ });
  it('is idempotent when called twice with the same idempotency key', async () => { /* ... */ });
});
Example — TYPESCRIPT
// Testing standards document (inline as test file pattern)

/**
 * TESTING STANDARDS — applies to all tests in this codebase
 *
 * Required for every PR:
 * - New business logic: unit tests
 * - New API routes: integration tests for all HTTP status codes
 * - New user flows: E2E test for the happy path
 * - Bug fixes: regression test that reproduces the bug
 *
 * Test naming convention:
 * it('[action/event] [expected result]', ...)
 * Example: it('returns 401 when token has expired', ...)
 *
 * Coverage targets:
 * - Auth and payments: 95%+
 * - API routes: 85%+
 * - UI components: 70%+
 *
 * PR reviewers must verify:
 * - Test assertions are specific and meaningful
 * - Error paths are tested, not just happy paths
 * - No new flaky tests are introduced
 */

// Example of standards applied:
describe('PaymentService.charge', () => {
  it('returns charge ID on successful payment', async () => { /* ... */ });
  it('throws InsufficientFundsError when card is declined', async () => { /* ... */ });
  it('does not expose full card number in error messages', async () => { /* ... */ });
  it('creates an audit log entry for every charge attempt', async () => { /* ... */ });
  it('is idempotent when called twice with the same idempotency key', async () => { /* ... */ });
});