Flag for tests not applicable to current series
Bug #913812 reported by
Max Brustkern
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| QA Regression Testing |
In Progress
|
Medium
|
Unassigned | ||
Bug Description
Is there any method for flagging tests cases that no longer apply to the current series? Removing the test doesn't make sense as long as it works in some supported series, but some sort of indication that it isn't expected to install or run in the current series could be useful for the automated test runners we're using on the QA team. If nothing else is suggested, I propose
# QRT-Deprecated
This currently appears to apply to test-opie.py (after Natty,) test-zope3.py (after Hardy,) test-python2.4 (after Hardy,) test-python2.5 (after Hardy,) test-python3.1 (after Natty,) and test-ruby1.9 (after Lucid.) I can provide a patch if the idea is accepted.
| Changed in qa-regression-testing: | |
| status: | New → Opinion |
| summary: |
- opie not installable in Oneiric, Precise + Flag for tests not applicable to current series |
| description: | updated |
| tags: | added: qa-test-code |
| description: | updated |
| description: | updated |
Revision history for this message
| Steve Beattie (sbeattie) wrote | #1 |
| Changed in qa-regression-testing: | |
| importance: | Undecided → Medium |
| status: | Opinion → In Progress |
Revision history for this message
| Max Brustkern (nuclearbob) wrote | #2 |
Revision history for this message
| pawciobiel (pawciobiel) wrote | #3 |
To post a comment you must log in.
Hi Max,
As an aside, the Opinion status is for when there's a dispute as to whether the issue is actually a bug. It is treated as a closed bug in launchpad, making it not show up in the default bug listing for a project.
In discussing it with the security team, something like this would probably be reasonable. I assume the QRT-Deprecated flag would take a release version in which the test became deprecated? We may have a weird issue where for some reason a package gets removed for a release or more and then comes back into the archive; netbeans is an example of a package doing this, though we don't have a test script for it.
Thanks!