🌐 Test Target (UNCHANGED — MANDATORY)

https://buggy.justtestit.org

⚠️ This site is intentionally buggy and designed for learning software testing.
Unexpected and inconsistent behavior is normal.

---

🎓 Module Purpose

This module simulates what happens after exploratory testing in a real QA team.

You are transitioning from:

"I explored and found issues"

to:

"I can design structured tests and communicate failures professionally."

This module focuses on discipline, clarity, and repeatability — not discovery.

---

🎯 Learning Objectives

By completing this module, you will be able to:

• Translate exploratory knowledge into formal test cases
• Design clear, repeatable, reviewable tests
• Execute only what is designed (no exploration)
• Report bugs in a professional, developer-friendly way
• Demonstrate scope discipline and QA judgment
• Reflect honestly on test quality and coverage

---

🔁 CRITICAL: Scope Continuity Rule (NON-NEGOTIABLE)

🚫 No New Areas Allowed

You MUST use the same TWO functional areas that you selected in:

Module 3 — Phase 2: Charter-Based Exploratory Testing

❌ You may NOT choose new features
❌ You may NOT expand coverage
❌ You may NOT switch areas
❌ You may NOT test outside previous charters

This simulates real projects:

Once scope is agreed, QA does not redefine it independently.

📌 Failure to follow this rule = assignment failure

---

⏱️ Timebox Policy (STRICT & HONEST)

⏳ Total Effort: ~10 Hours (Hard Cap)

Phase	Focus	Timebox
Phase 1	Test Case Design	5 hours
Phase 2	Test Execution & Bug Reporting	3 hours
Phase 3	QA Reflection & Judgment	2 hours

⚠️ Same honesty rules as Module 3 apply
⚠️ No work outside assigned time
⚠️ No "just checking something quickly"

---

🧠 Scenario

After your exploratory testing, your QA lead says:

"Good findings.
Now we need structured coverage that we can reuse, review, and regress."

Your job is not to explore more —
Your job is to formalize what matters.

---

🧪 Phase 1: Test Case Writing (NO EXECUTION)

⏳ Timebox: 5 Hours

---

🎯 Goal

Design professional test cases based ONLY on:

• Your previous exploratory findings
• Your charter focus areas
• Observed system behavior

---

🔐 Rules (IMPORTANT)

You MUST:

• Design test cases only
• Stick strictly to your 2 previous charter areas
• Write test cases as if someone else will execute them

You MUST NOT:

• Execute tests
• Explore the system
• Add new scopes or flows
• Validate assumptions during this phase

---

📌 Scope Reminder (Example)

If in Module 3 you selected:

• Charter A: Search & Filtering
• Charter B: User Registration & Login

Then in THIS module:
✅ Only Search & Filtering
✅ Only User Registration & Login
❌ No ratings
❌ No car detail pages
❌ No navigation testing

---

📝 Test Case Requirements

📊 Quantity

• 10–15 test cases per area
• Total: 20–30 test cases

---

📋 Mandatory Test Case Format

Each test case MUST include:

Field	Required
Test Case ID	✅
Title	✅
Preconditions	✅
Test Steps	✅
Test Data	✅ (if applicable)
Expected Result	✅
Priority (High / Medium / Low)	✅
Type (Positive / Negative / Boundary)	✅

⚠️ Expected Results must describe system behavior
❌ "Works fine" / "As expected" are INVALID

---

▶️ Phase 2: Test Execution & Bug Reporting

⏳ Timebox: 3 Hours

---

🎯 Goal

Execute only the test cases you designed and report only genuine failures.

---

🔐 Rules (STRICT)

You MUST:

• Execute tests exactly as written
• Log bugs only when Expected ≠ Actual
• Reference the related Test Case ID

You MUST NOT:

• Perform exploratory testing
• Add or modify test cases
• Extend scope
• Test "just to see"

Finishing early does NOT mean you test more.

---

🐞 Bug Reporting Requirements

📝 Mandatory Bug Report Format

Each bug MUST include:

• Title
• Preconditions
• Steps to Reproduce
• Expected Result
• Actual Result
• Severity (Low / Medium / High)
• Evidence (screenshot / recording)
• Related Test Case ID

📌 No minimum bug count
📌 Bug quality matters more than quantity

---

🧠 Phase 3: QA Reflection & Judgment

⏳ Timebox: 2 Hours

---

📄 Required Written Analysis (1–2 Pages)

You MUST answer ALL sections:

---

1️⃣ Test Case Quality Review

• Which test cases were effective?
• Which were unclear or redundant?
• What would you redesign?

---

2️⃣ Bug Quality Review

• Were the failures easy to reproduce?
• Did Expected Results help or confuse?
• Any bug reports you would rewrite?

---

3️⃣ Coverage & Remaining Risk

• What important behavior remains untested?
• What risks still worry you?
• Which area should be automated first — and why?

---

⭐ Honest Self-Critique (BONUS SCORE)

Answer honestly:

• Where you over-designed
• Where you under-thought
• Where test cases added little value

There is no penalty for honesty.
There is a penalty for pretending everything was perfect.

---

🕒 REQUIRED: Time Usage Report

Provide an honest breakdown.

Phase	Activity	Time
Phase 1	Test case design	Xh
Phase 2	Execution	Xh
Phase 2	Bug writing	Xh
Phase 3	Reflection	Xh

Reflection Questions

• Where did I waste time?
• Where did I under-invest?
• What would I change next time?

---

📊 Evaluation Criteria

Area	Focus
Test Case Design	Clarity & correctness
Scope Discipline	Respecting boundaries
Bug Reporting	Precision & usefulness
QA Judgment	Risk awareness
Time Honesty	Professional integrity
Reflection	Maturity & self-awareness

---

🌱 Core Lesson of This Module

Exploratory testing discovers problems.
Test cases prevent them from returning.

Strong QA is not about finding more.
It is about thinking clearly under constraint.