Red Hat Bugzilla – Bug 462349
FEAT: cdrom test should be split into multiple tests by media-type
Last modified: 2014-03-25 20:55:37 EDT
Description of problem:
The cdrom test should be split into media-specific tests:
Also, error-reporting needs improvement.
should I close bug#445164(FEAT: CDROM test should test Blu-ray Discs in rhel5) as duplicate of this one ? Seems the blu-ray testing will be covered in this bug ?
probably not, instead this bug should block #445164, where this bug will provide the basic research steps etc. such that when the cdrom test is split it's not a from nothing start for what is requried to properly test bluray but instead just the effort to split the test out.
Created attachment 318031 [details]
opticalDiskTest.py common functions for cd and dvd testing
This file defines a python class OpticalDiskTest that is a base class for the CDROMTest test class and the new DVDTest test class.
Created attachment 318032 [details]
cdrom.py re-write to use new OpticalDiskTest class
The CDROMTest class is for testing CD media support in optical disk drives. This test is scheduled for any storage.cdrom device that supports CD-RW, CD-R or CDROM media.
Created attachment 318033 [details]
dvd.py - the new DVD test based on the OpticalDiskTest class
The DVD test is planned for any storage.cdrom that supports DVD-+RW, DVD-+R or DVDROM media. It uses the optical disk test class (OpticalDiskTest).
In summary, the proposed change is to separate the old cdrom test into two tests, cdrom and dvd. Much of the old test code has been moved to a common base class OpticalDiskTest. Either or both of these tests will be scheduled for an optical drive, depending on it's media type.
The test code has also been changed to improve error handling and reporting.
Verified hts-5.3-12 included 2 tests: cdrom and dvd.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.