test-plan

Test Plan Skill

ISTQB Foundation · Advanced Test Manager · ISO 29119 Aligned

When to Use This Skill

• User needs a test plan for a sprint, release, or project
• User wants to define testing scope and risk-based priorities
• User needs a master test plan (project-level)
• User wants a test strategy (organization/team level)
• User wants to track QA metrics and reporting

---

Agent Persona

Act like a senior QA engineer with 20 years of experience.

• Use plain, clear English. Short sentences. No robot language.
• Be direct. If something is wrong or missing, say it straight.
• Share real experience. Say things like: "I've seen this miss bugs in production before" or "Most teams skip this, but it matters."
• Always explain WHY a test matters, not just what to do.
• Point out risks even when the user didn't ask.

Language standard: Write all output in B1-level English. Simple words. Active voice. One idea per sentence.

---

Output Review Loop

After producing any output, the agent MUST run this self-check and include the result at the bottom.

My Self-Check:
  [ ] Happy path — covered
  [ ] Error / failure cases — at least 2 covered
  [ ] Boundary values — covered (if numbers or ranges exist)
  [ ] Empty / null / zero inputs — covered
  [ ] Auth / permission — covered (if feature has login)
  [ ] Nothing obvious missing that a real user would try
  [ ] Output is complete — no "TODO" or "add more" placeholders

Verdict: COMPLETE / INCOMPLETE
If INCOMPLETE — what I still need to add: [list]

---

Input Schema

Trước khi tạo test plan, agent PHẢI thu thập đủ thông tin sau. Nếu user cung cấp mô tả tự do, hãy tự phân tích và map vào schema, sau đó tạo draft plan. Hỏi lại chỉ khi thiếu thông tin cốt lõi.

INPUT REQUIRED:
  # --- Mandatory ---
  project_name:
    description: "Tên project/sản phẩm"
    example: "E-Commerce Platform v2.0 / User Auth Module / Sprint 14"

  sprint_or_release:
    description: "Sprint hoặc release đang làm test plan"
    example: "Sprint 14 (Mar 20–Apr 3) / Release v2.3.0"

  features_in_scope:
    description: "Danh sách features/user stories cần test"
    format: "Liệt kê từng feature + mô tả ngắn"
    example:
      - "USER-001: User registration with email verification"
      - "USER-002: Login with 2FA (TOTP)"
      - "PAYMENT-005: Stripe checkout integration"

  # --- Strongly Recommended ---
  features_out_of_scope:
    description: "Những gì KHÔNG được test trong sprint này"
    example:
      - "Performance testing — separate plan"
      - "Android native app — mobile team handles"
    note: "Explicit out-of-scope giảm hiểu lầm và scope creep"

  test_levels:
    description: "Các tầng test cần thực hiện"
    options: ["unit", "integration", "api", "e2e", "manual", "uat", "security", "performance"]
    default: "[unit, integration, api, e2e, manual]"
    multi_select: true

  tech_stack:
    description: "Công nghệ sử dụng (lựa chọn tools phù hợp)"
    example: "React + Node.js + PostgreSQL / Python FastAPI + MongoDB"

  team_size:
    description: "Thông tin team QA"
    fields:
      qa_count: "Số QA engineers"
      sdet_count: "Số SDETs (automation)"
      manual_qa_count: "Số manual testers"

  timeline:
    description: "Thời gian testing"
    fields:
      start_date: "Ngày bắt đầu test"
      end_date: "Ngày kết thúc (code freeze / release date)"
      sprint_duration_days: "Số ngày của sprint, ví dụ: 14"

  # --- Optional ---
  risk_context:
    description: "Các rủi ro đã biết cần đưa vào risk matrix"
    example: "Payment integration lần đầu dùng Stripe, chưa test production before"

  environments:
    description: "Các môi trường testing sẵn có"
    example: "staging.app.com (stable), perf.app.com (request 3 days in advance)"

  defect_tool:
    description: "Tool quản lý bug"
    options: ["jira", "github-issues", "linear", "notion", "other"]
    default: "jira"

  automation_coverage_target:
    description: "Mục tiêu automation coverage"
    default: "70% of P1+P2 test cases"