[Fedora QA] #35: Sync up install test priorities with the release criteria

[Fedora QA]

#35: Sync up install test priorities with the release criteria
--------------------------+-------------------------------------------------
  Reporter:  jlaska       |       Owner:  jlaska   
      Type:  task         |      Status:  assigned 
  Priority:  major        |   Milestone:  Fedora 13
 Component:  Test Review  |     Version:           
Resolution:               |    Keywords:           
--------------------------+-------------------------------------------------
Comment (by jlaska):

 After reorganizing the test cases using the release criteria as a guide,
 the following tests I was unable to easily fit into the Alpha, Beta or
 Final priority.

 > Package Set
  *
 [https://fedoraproject.org/wiki/QA/TestCases/PackageSetsMinimalPackageInstall
 QA/TestCases/PackageSetsMinimalPackageInstall]

 I'd actually like to remove this test.  It's original intent was to
 capture what the critical path package set is better capturing now.  I
 don't think we lose anything since we'll continue to have the ''Default
 Package Install'', repoclosure and conflict tests on the list.

 > User Interface
  *
 [https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_Cmdline
 QA:Testcase_Anaconda_User_Interface_Cmdline]
  *
 [https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_serial_console
 QA:Testcase_Anaconda_User_Interface_serial_console]
  *
 [https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_Telnet
 QA:Testcase_Anaconda_User_Interface_Telnet]

 I know the installer team would like to stop supporting some of these
 funky options (e.g. telnet), I'd like to keep this on the list as long as
 they continue to be supported.  Any thoughts on the appropriate priority?

 > Upgrade system
  *
 [https://fedoraproject.org/wiki/QA:Testcase_Preupgrade_from_older_release
 QA:Testcase_Preupgrade_from_older_release]

 Upgrading from a the CURRENT-2 release is not explicitly listed in the
 release criteria.  Does that mean this can be dropped?

 > Partitioning
  *
 [https://fedoraproject.org/wiki/QA/TestCases/PartitioningUninitializedDisks
 QA/TestCases/PartitioningUninitializedDisks]

 This test correctly captures the specific scenario when anaconda does not
 recognize the disks and prompts to initialize them.  I'd like to propose
 moving this to Alpha.  The use case captured is when you are installing on
 a new blank hard drive.  Thoughts?

 > Recovery
  *
 [https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_installation_source
 QA:Testcase_Anaconda_updates.img_via_installation_source]
  *
 [https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_local_media
 QA:Testcase_Anaconda_updates.img_via_local_media]
  * [https://fedoraproject.org/wiki/QA:Testcase QA:Testcase] Anaconda
 traceback debug mode

 Again, I think these are important tests, but I'm unclear on the priority.
 Just picking something ... beta?

-- 
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/35#comment:7>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance