#72: Proposal for reducing test permutations
--------------------------+-------------------------------------------------
Reporter: rhe | Owner: rhe
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Test Review | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------------------
Comment (by rhe):
Replying to [comment:7 jlaska]:
<skip>
Hurry: I think we'll need to keep the minimal install test around for
Fedora 14. However, I don't think we need to run this test for *every*
usage scenario. Can both the default package set, and the minimal package
set tests be moved into the general variations list? I don't think these
need to be tested against each boot+install method.
No problem. Having default package set test in each scenario is easier for
testers to add results. I don't think it's specific to any usage scenario
as well, so I'll put it in general list.
Additionally, I've updated the
[
https://fedoraproject.org/wiki/QA/TestCases/PackageSetsMinimalPackageInstall
minimal install package set test] to ensure the system is able to access
the network and install yum updates.
Thanks to both you and Adam for clarifying this issue, let's keep minimal
install test.
> "Reason: I think the other partitioning tests and
QA/TestCases/BootMethodsKVM(Install on a new created kvm) have somehow
covered this test. "
I'd really like to also remove 'QA/TestCases/BootMethodsKVM' and it's
XEN counterpart, or at least rename them to something more appropriate.
Perhaps a set of storage device tests that confirm the detection and use
of virt storage and network devices?
I'm going to remove them and add a case
[
https://fedoraproject.org/wiki/QA:Testcase_Install_to_KVM
QA:Testcase_Install_to_KVM] instead.Thanks.
--
Ticket URL: <
https://fedorahosted.org/fedora-qa/ticket/72#comment:9>
Fedora QA <
http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance