Efficient testing of install images
The number of images to test is increasing rapidly, and some images require specific hardware which is not widely available in the community. These factors make it impractical to do exhaustive testing of install images. However, adequate coverage must still be acheived in order to ensure the quality of milestone images.
Blueprint information
- Status:
- Complete
- Approver:
- David Mandala
- Priority:
- Medium
- Drafter:
- Paul Larson
- Direction:
- Approved
- Assignee:
- Paul Larson
- Definition:
- Approved
- Series goal:
- Accepted for lucid
- Implementation:
- Implemented
- Milestone target:
- lucid-alpha-2
- Started by
- Paul Larson
- Completed by
- Paul Larson
Whiteboard
[asac 24-11-09]: added a high level perspective to the "Design" section of the spec + approved.
[asac 12-01-09]: tentatively targetting for alpha-2 with option to push to alpha-3 as establishing a standard QA team process might take some time.
[plars 01-05-10]: http://
[plars 01-05-10]: milestones are created on iso tracker, but are not available until after hardy.4 testing is complete (sometime around Feb 4
[plars 02-01-10]: milestones are now visible and activated on iso tracker, testing in progress
Work Items lucid-alpha-2:
Create a list of install options for ARM: DONE
Create matrix of minimum tests required to test each option and each pair: DONE
Document install test scenarios on testcases.
Work items lucid-alpha-3:
Create virtual milestones for post-milestone testing: DONE
Schedule tests as appropriate for each virtual milestone: DONE
Status:
Implemented.