#72: Proposal for reducing test permutations
--------------------------+-------------------------------------------------
Reporter: rhe | Owner: rhe
Type: enhancement | Status: closed
Priority: major | Milestone: Fedora 14
Component: Test Review | Version:
Resolution: fixed | Keywords:
--------------------------+-------------------------------------------------
Changes (by rhe):
* status: new => closed
* resolution: => fixed
Comment:
Replying to [comment:11 jlaska]:
> Apologies, I missed your latest updates in this ticket.
No worries.
> Replying to [comment:10 rhe]:
> > I further updated the
[https://fedoraproject.org/wiki/User:Rhe/Draft2#Test_Matrix matrix], and
I'm not sure if the following tests can be removed or not:
> >
> > *
[https://fedoraproject.org/wiki/QA:Testcase_Boot_Methods_efidisk.img
QA:Testcase_Boot_Methods_efidisk.img]
> >
> > Reason: Not commonly used and require special device to support it.
>
> I'd like to remove this test, but I'm afraid we need to ensure this is
functional since it is included in the Beta release criteria
(https://fedoraproject.org/wiki/Fedora_14_Beta_Release_Criteria). I've
relied on feedback from pjones in previous releases to run this test.
Mainly because running this test is still a mystery to me. I agree the
conditions around this test are not ideal, but I don't have any great
ideas for improving this right now :(
I see, since it's included in beta criteria, let's keep this test.
> > * [https://fedoraproject.org/wiki/QA/TestCases/PartitioningNoSwap
QA/TestCases/PartitioningNoSwap]
> >
> > Reason: I don't think No Swap should be separated as a test.
>
> This test still exists to target the dialog warning that swap is
recommended. What do you recommend, should this test be absorbed into
another test?
Hmm, I think it depends on the importance of no swap partitioning. A
possible way is to absorb this into the expected results of ext4 and ext3
partitioning tests, saying "If no swap partition is given, a warning
dialogue will pop up...", but then no swap is not guaranteed to be tested.
So, I think just keeping this test is fine.
> > *
[https://fedoraproject.org/wiki/QA/TestCases/KickstartKsFilePathKsCfg
QA/TestCases/KickstartKsFilePathKsCfg]
> >
> > Reason: Is it a usual way to load kickstart file? I seldom use this
way.
>
> This is how preupgrade and snake delivery kickstarts. They open up the
initrd.img and insert the ks.cfg there. We'll need to continue supporting
this.
I understand now.
> > *
[https://fedoraproject.org/wiki/QA:Testcase_Preupgrade_low_/boot_disk_space_to_install
QA:Testcase_Preupgrade_low_/boot_disk_space_to_install]
> >
> > Reason:
[https://fedoraproject.org/wiki/QA:Testcase_Preupgrade_from_older_release
QA:Testcase_Preupgrade_from_older_release] is already the case of low
/boot disk space. And for upgrading from F13, 500M /boot is enough for
preupgrading.
>
> Good point, this should be less of an issue preupgrading from F13 ->
F14. The remaining preupgrade test is written to mimic a real-world
upgrade scenario, so we should capture any /boot size issues as they
surface.
Okay, I'll remove
[https://fedoraproject.org/wiki/QA:Testcase_Preupgrade_low_/boot_disk_space_to_install
QA:Testcase_Preupgrade_low_/boot_disk_space_to_install]
Thank you all. I'm closing this ticket. Feel free to reopen in need.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/72#comment:12>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
