Ubuntu

Fixed bug verification

Registered by Henrik Nilsen Omma

Some high profile or fundamental bugs that have been fixed during the development cycle or previous releases should be tested for when we do ISO testing.

Agenda:

 * Criteria and methods for identifying these bugs
 * Manual testing:
  * Writing test cases (who? developer who fixed bug?)
  * Scheduling, performing and tracking testing
 * Automated testing:
  * Which bugs are suitable?
  * How and by whom will test be written?
  * What outstanding infrastructure does this depend on?

Blueprint information

Status:
Complete
Approver:
Henrik Nilsen Omma
Priority:
Medium
Drafter:
Brian Murray
Direction:
Approved
Assignee:
Steve Beattie
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Henrik Nilsen Omma
Completed by
Henrik Nilsen Omma

Related branches

Sprints

Whiteboard

heno 2007-11-16: ready for review

heno 2008-05-29: Assignment transfered to Steve Beattie. This is a prerequisite for fix-validation-tracking

heno 2008-06-16: We thought we would merge this spec in with fix-validation-tracking, but it's not as good of a match as we thought. We will leave the late-fix checking in the wiki for this cycle and revisit it post-intrepid where we will likely extend the archive view of the fix-validation-tracking spec to cover this. The wiki version of this tracking was actually implemented here: https://wiki.ubuntu.com/Testing/FixesToVerify We had hijacked this spec for Intrepid, but we'll put it back now and revisit late-fix checking in Intrepid+1

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.