Test Architecture — Animate | AI Wisdom

← Back to topic
🎞 ANIMATE · Mode 3 of 5 · +100 XP— Test Architecture
📋Test Pyramid
⚙️Factories
🔄Helpers
✅Matchers
🎯 Next: Test →
Step 1 / 4
Speed
Test Pyramid
Pyramid shape: many unit, some integration, few E2E tests💡 Analogy
Like building inspections — many quick material checks, fewer structural tests, only a few full walk-throughs.
The test pyramid: lots of fast unit tests at the base, fewer integration tests in the middle, and a small number of slow E2E tests at the top.
Console Output
> unit tests: 200+ tests, <5s total
> integration tests: 30 tests, 30s total
> e2e tests: 10 tests, 5min total
●test-setup.ts
Test PyramidL1–5
1// Test pyramid: many unit, some integration, few E2E
2// tests/unit/          — fast, isolated, many
3// tests/integration/   — real DB/HTTP, fewer
4// tests/e2e/           — real browser, slowest, fewest
5 
6// Shared test utilities — avoid repetition
7// tests/helpers/user-factory.ts
8export const UserFactory = {
9  build: (overrides = {}) => ({
10    id: crypto.randomUUID(),
11    name: 'Test User',
12    email: 'test@example.com',
13    role: 'user' as const,
14    createdAt: new Date(),
15    ...overrides,
16  }),
17  create: async (db: Db, overrides = {}) => {
18    const data = UserFactory.build(overrides);
19    return db.users.insert(data);
20  },
21};
22 
23// Custom matchers — reusable assertions
24// vitest.setup.ts
25expect.extend({
26  toBeValidEmail(received: string) {
27    const pass = /^[^s@]+@[^s@]+.[^s@]+$/.test(received);
28    return {
29      pass,
30      message: () => pass
31        ? `Expected ${received} not to be a valid email`
32        : `Expected ${received} to be a valid email`,
33    };
34  },
35});
36 
37// Type augmentation for custom matcher
38declare module 'vitest' {
39  interface Assertion<R = any> {
40    toBeValidEmail(): R;
41  }
42}
42 lines
Timeline — 4 Steps
Test Pyramid
Pyramid shape: many unit, some integration, few E2E tests💡 Analogy
Like building inspections — many quick material checks, fewer structural tests, only a few full walk-throughs.
The test pyramid: lots of fast unit tests at the base, fewer integration tests in the middle, and a small number of slow E2E tests at the top.
Console Output
> unit tests: 200+ tests, <5s total
> integration tests: 30 tests, 30s total
> e2e tests: 10 tests, 5min total

Was this page helpful?

Discussion

Pyramid shape: many unit, some integration, few E2E tests

💡 Analogy

Like building inspections — many quick material checks, fewer structural tests, only a few full walk-throughs.

The test pyramid: lots of fast unit tests at the base, fewer integration tests in the middle, and a small number of slow E2E tests at the top.

Console Output

> unit tests: 200+ tests, <5s total
> integration tests: 30 tests, 30s total
> e2e tests: 10 tests, 5min total

Pyramid shape: many unit, some integration, few E2E tests

💡 Analogy

Like building inspections — many quick material checks, fewer structural tests, only a few full walk-throughs.

The test pyramid: lots of fast unit tests at the base, fewer integration tests in the middle, and a small number of slow E2E tests at the top.

Console Output

> unit tests: 200+ tests, <5s total
> integration tests: 30 tests, 30s total
> e2e tests: 10 tests, 5min total