action #20830
closed
[tools][sles][functional]Get rid of version specific prefix in test suite names when the test suites also apply for other versions
Added by okurz almost 7 years ago.
Updated over 6 years ago.
Category:
Enhancement to existing tests
Estimated time:
(Total: 0.00 h)
Description
Currently we have test suites like "sles12_qa_acceptance_fs_stress". IMHO the prefix "sles12_qa_acceptance" does not provide any useful meaning. Obviously we are doing "QA" here, the test suite also applies for sle15 so "sles12" is misleading. And "acceptance" is not really helpful because all tests could provide a result which influences "acceptance" but could also show other problems. I suggest we just get rid of this prefix in test suites. Any objections?
- Copied from action #18936: [tools][sles][functional] Enable 3 stress acceptance on s390x added
Asked sero in #testing if he would mind
Sorry, the hard disk of my laptop was broken. I just notice this ticket. I'm fine with the name change, it's reasonable to change the name in openQA platform, because they actually some stress test. I remember, as a user, Marita also said them as stress test, then I think they should be.
But we will still keep the old name under my team's test package, since we have different types of test against kernel. It's better to remind us that they are for acceptance test.
If you like I can change the name for you, or you can remove the prefix directly.
- Related to coordination #20944: [sle][functional][epic] Get rid of architecture specific test suites added
- Status changed from Feedback to In Progress
- Assignee changed from okurz to riafarov
Ok, so I renamed the three testsuites which are just called process_stress, fs_stress, sched_stress now.
I added the sle15 hdd image creation job accordingly to START_AFTER_TEST which should prevent some incompletes on current SLE15 builds.
I deleted the …_s390x variants as we have proper image creation jobs now relying only on the SDK repo and not ISO, therefore the downstream jobs do not need to be duplicated anymore, see #20944 for details.
@riafarov for continuing with "sles12_autoyast…" testsuites which are also triggered for SLE15.
- Status changed from In Progress to Feedback
On hold as we will probably end up with different profiles for sle 15.
- Related to action #23736: [sle][functional] Adjust autoinst profiles for sle 15 added
- Status changed from Feedback to In Progress
- Assignee deleted (
riafarov)
I take care of autoyast profiles in #23736
How is this in progress while there is no Assignee? :)
Our ticket workflow is described on https://progress.opensuse.org/projects/openqav3/wiki/Wiki#ticket-workflow . "In Progress: Any state between New and Resolved. The ticket has been refined and is ready to be picked." In this case riafarov worked on the ticket, did one step and leaves the ticket for someone else to continue the work. But honestly I am also not so sure why @riafarov unassigned.
@riafarov: hint: Better mention tickets with # and not complete URLs so that redmine can provide a preview.
- Related to coordination #17714: [sles][functional][medium][epic] various testsuite enhancements (names, descriptions, etc.) added
The only remaining test suites with versions in the name are autoyast. Our proposal is to move it to separate job group. The only undecided part is if it should be separate one, or we keep same one we have in Development.
discussed in M10 review, will move to M11, still applies for SLE15 setup tasks
- Target version changed from Milestone 10 to Milestone 11
- Status changed from In Progress to Feedback
- Assignee set to okurz
- Target version changed from Milestone 11 to Milestone 12
We made some progress and have a good idea how to adjust the profiles for autoyast but as of now are not done yet, maybe in the next days, see #23736. But we have a confidence we should be able to close this within the next milestone so shifting.
- Status changed from Feedback to Resolved
All seems good now for SLE15 as well as SLE 12 SP4
Also available in: Atom
PDF