STAGE 1: Understand the requirement
Concept: Testing starts with expected behavior and risk.
Task: Turn booking requirements into a traceable test list; identify missing rules.
Acceptance: Do not invent expected behavior without marking an assumption.

My assumptions:

My work / file link:

My checks and results:

What I changed:


STAGE 2: Design useful cases
Concept: Equivalence classes and boundaries reduce redundant tests.
Task: Test required fields, email format, capacity and duplicate submission.
Acceptance: Include positive, negative and boundary examples.

My assumptions:

My work / file link:

My checks and results:

What I changed:


STAGE 3: Report reproducible defects
Concept: A good defect report separates observation from diagnosis.
Task: Write two reports with steps, data, expected/actual results and impact.
Acceptance: Do not state a root cause unless investigated.

My assumptions:

My work / file link:

My checks and results:

What I changed:


STAGE 4: Assess readiness
Concept: A pass rate alone does not establish release quality.
Task: Summarize coverage, unresolved risks and known limitations.
Acceptance: A severe unresolved defect is visible even when most tests pass.

My assumptions:

My work / file link:

My checks and results:

What I changed:
