testing-strategy

Testing Strategy Skill

단위 테스트를 넘어 통합/E2E/계약 테스트를 설계하는 스킬입니다.

테스트 피라미드

        /  E2E  \        ← 적게, 핵심 플로우만
       /  통합   \       ← 중간, 컴포넌트 간 연동
      /   단위    \      ← 많이, 빠르고 격리

계층	비중	속도	범위
단위	70%	빠름 (ms)	함수/메서드
통합	20%	중간 (s)	컴포넌트 간
E2E	10%	느림 (min)	전체 시스템

통합 테스트

데이터베이스 통합

func TestUserRepo_Integration(t *testing.T) {
    if testing.Short() {
        t.Skip("통합 테스트 건너뜀")
    }
    db := setupTestDB(t)
    defer db.Close()

    repo := NewUserRepo(db)
    user, err := repo.Create(ctx, &User{Name: "test"})
    require.NoError(t, err)

    found, err := repo.FindByID(ctx, user.ID)
    require.NoError(t, err)
    assert.Equal(t, "test", found.Name)
}

HTTP API 통합

func TestAPI_CreateUser(t *testing.T) {
    srv := setupTestServer(t)
    defer srv.Close()

    resp, err := http.Post(srv.URL+"/api/v1/users",
        "application/json",
        strings.NewReader(`{"name":"test"}`))
    require.NoError(t, err)
    assert.Equal(t, http.StatusCreated, resp.StatusCode)
}

E2E 테스트

핵심 플로우만 테스트

사용자 등록 → 로그인 → 리소스 생성 → 조회 → 삭제

QAMESH Source Guidance

• QAMESH is the default project QA orchestration layer. Playwright is not a competing mode; when detected, it is registered as a browser/gui Journey runner adapter.
• Ask users to choose the project under test, execution authority, environment/origin, credentials boundary, mobile/cloud device boundary, or explicit canary command. Do not ask them to choose between QAMESH and Playwright.
• Use auto qa init --format json as the simple default release-QA setup command for arbitrary projects. It creates project-local starter Journey Packs plus a generic GitHub Actions QAMESH release gate.
• Use auto qa init --local-only --format json when only Journey Pack starters are needed. Review generated commands, env, installer version, and required-gate policy before trusting the workflow.
• Use auto qa plan --format json before project-level QA execution to inspect Journey Packs, detected adapters, selected lanes, setup gaps, and output paths without running commands.
• Use auto canary only for post-deploy smoke/status verification. QAMESH owns deterministic user journey evidence, redacted artifacts, run indexes, and repair feedback; auto qa release treats canary-explicit as a bridge lane for an explicit post-deploy smoke Journey Pack.
• Use auto qa run --format json when deterministic project QA should execute and produce QAMESH run/evidence output.
• Use auto qa explore --dry-run --format json before GUI exploration; execute it only for explicit local/staging Journey Packs with allowed origins, forbidden actions, deterministic oracles, and redacted artifact retention.
• Use auto qa scenario compile --format json to turn project-declared user scenarios in .autopus/qa/scenarios/*.yaml into Playwright specs; the step vocabulary is read-only by construction, so a compiled scenario cannot trip the GUI forbidden-action guard.
• Use auto qa release --dry-run --format json to inspect the fixed release lane set, setup gaps, blocker matrix, redacted command previews, and sibling SPEC readiness before launch gates; use auto qa release --roadmap --format json for the canonical roadmap surface.
• Use auto qa evidence when an external producer already wrote a QAMESH manifest and the task is validation, redaction, and publication.
• Use auto qa feedback to turn existing failed QAMESH evidence into provider-specific repair prompt bundles.
• ADK is a harness: each concrete Journey Pack is a project-local Journey Pack under .autopus/qa/journeys/**, while ADK owns adapters, execution, redaction, and feedback plumbing.