Knowledgebase

Planning Testing for a Release Print

  • softwaretestingqa, software, guide, howto, solution, zillionkinghost, hosting, support
  • 0

Organising the work.

WHAT TO ESTABLISH

What changed What those changes could affect What must be verified What time is available

WHAT TO PRIORITISE

Changed areas Areas depending on them Areas with defect history Critical paths, always

WHAT TO PRODUCE

A plan naming what will be tested and by whom.

WHAT TO INCLUDE

Entry conditions: what must be ready

Exit conditions: what must be true to release

Environments and data required Risks and what is not covered

WHAT ENTRY CONDITIONS PREVENT

Testing a build that is not ready, which wastes effort.

WHAT TO AGREE ABOUT DEFECTS

What severity blocks release.

WHEN TO AGREE IT

Before testing, not during.

WHY

Under pressure the answer shifts.

WHAT TO TRACK DURING

What has been tested What remains What was found

WHAT TO COMMUNICATE DAILY

Progress, and anything that changes the risk picture.

WHAT TO DO WHEN TIME RUNS SHORT

Reduce scope deliberately, and say what was dropped.

WHAT TO NEVER DO

Silently skip planned testing.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot