Establish a rigorous, standardised testing procedure for potential releases

Registered by Marc Stewart

A few bugs have been caught just after—rather than before—release, resulting in point releases that could have been avoided if there had been an established test procedure to follow each time. Obviously, the implementation of new features will result in new tests becoming necessary so there is still potential for things to be missed, but a routine inspection prior to each release should help to minimise future problems.

Blueprint information

Status:
Started
Approver:
None
Priority:
Essential
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Marc Stewart

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.