User:Jskladan/Sandbox:F18 Criteria Testcases Beta

From FedoraProject

Jump to: navigation, search
  1. All Fedora 18 Alpha Release Criteria must be met
  2. All bugs blocking the Beta tracker must be CLOSED
  3. The network installation image, DVD image, and live images for release-blocking desktops must meet current size requirements QA:Testcase_Mediakit_ISO_Size
  4. The installer must boot (if appropriate) and run on all primary architectures, with all system firmware types that are common on those architectures, from default live image, DVD, and boot.iso install media when written to a USB stick with any of the officially supported methods Test_Results:Fedora_18_Beta_TC6_Install?rd=Test_Results:Current_Installation_Test#USB_Stick
  5. ??The installer must be able to use the HTTP, FTP and either NFS or NFSISO remote package source options QA:Testcase_install_repository_NFS_variation QA:Testcase_install_repository_NFSISO_variation (Marked as Final)
  6. ?? It must be possible to install by booting the installation kernel directly, including via PXE, and correctly specifying a remote source for the installer itself, using whichever protocols are required to work for package retrieval at the current phase (Alpha, Beta, Final). This must work if the remote source is not a complete repository but contains only the files necessary for the installer itself to run. QA:Testcase_Boot_Methods_Pxeboot (Marked as Alpha)
  7. The installer must be able to complete an installation using the serial console interface QA:Testcase_Anaconda_User_Interface_serial_console
  8. The installer must be able to use all kickstart delivery methods QA:Testcase_Kickstart_File_Path_Ks_Cfg QA:Testcase_Kickstart_Http_Server_Ks_Cfg QA:Testcase_Kickstart_Nfs_Server_Path_Ks_Cfg QA:Testcase_Kickstart_Hd_Device_Path_Ks_Cfg
  9. ?? The installer must be able to complete an installation using automatic partitioning to a validly-formatted disk with sufficient empty space, using the empty space and installing a bootloader but leaving the pre-existing partitions and data untouched Testcases as #12 Alpha criterion; Testcases do not mention that pre-existing partitions must be untouched
  10. Skipping this on, as there still is debate about partitioning on the test listThe installer's custom partitioning mode must be capable of the following:
    • Creating, destroying and assigning mount points to partitions of any specified size using most commonly-used filesystem types
    • Creating encrypted partitions
    • Rejecting obviously invalid operations without crashing
  11. The installer must be able to create and install to software, hardware or BIOS RAID-0, RAID-1 or RAID-5 partitions for anything except /boot QA:Testcase_Install_to_Hardware_RAID QA:Testcase_Install_to_BIOS_RAID QA:Testcase_Partitioning_On_Software_RAID
  12. Skipping this on, as there is currently no way to upgrade.For each one of the release-blocking package sets ('minimal', and the package sets for each one of the release-blocking desktops), it must be possible to successfully complete an upgrade from a fully updated installation of the previous stable Fedora release with that package set installed, using any officially recommended upgrade mechanisms. The upgraded system must meet all release criteria.
  13. The installer must be able to successfully complete a scripted installation, using the installer's preferred scripting system, which duplicates the default interactive installation as closely as possible as #8
  14. Any installation method or process designed to run unattended must do so (there should be no prompts requiring user intervention)Kickstarts?
  15. The rescue mode of the installer must be able to detect and mount (read-write and read-only) LVM, encrypted, and RAID (BIOS, hardware, and software) installations QA:Testcase_Anaconda_rescue_mode
  16. ?? When booting a system installed without a graphical environment, or when using a correct configuration setting to cause an installed system to boot in non-graphical mode, the system should provide a working login prompt without any unintended user intervention when boot is complete, and all virtual consoles intended to provide a working login prompt should do so This is exactly the same as #19 Aplha criterion, maybe we'd like to leavit just Alpha or Beta
  17. The release must be able host virtual guest instances of the same release, using Fedora's current preferred virtualization technology QA:Testcase_Install_to_Current_KVM
  18. The release must install and boot successfully as a virtual guest in a situation where the virtual host is running the previous stable Fedora release, using Fedora's current preferred virtualization technology QA:Testcase_Install_to_Previous_KVM
  19. In most cases, the installed system must be able to play back sound with gstreamer-based applications (see Blocker_Bug_FAQ) QA:Testcase_audio_basic
  20. No part of any release-blocking desktop's panel (or equivalent) configuration should crash or be entirely non-functional on boot of the installed system using default installation choices QA:Testcase_desktop_panel_basic
  21. Automatic mounting on insertion of removable media must work in release-blocking desktops QA:Testcase_desktop_automount
  22. The default update manager in release-blocking desktops must not periodically check for updates when the system is booted live, but must periodically check for updates when running on an installed system QA:Testcase_desktop_updates
  23. ?? All release-blocking desktops' offered mechanisms (if any) for shutting down, logging out and rebooting must work IMHO no testcase coveres this