From Fedora Project Wiki
(Created page with "# All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f18alpha&hide_resolved=1 Alpha tracker] must be CLOSED #...") |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
# All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f18alpha&hide_resolved=1 Alpha tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]] | # All bugs blocking the [https://bugzilla.redhat.com/showdependencytree.cgi?id=f18alpha&hide_resolved=1 Alpha tracker] must be [[BugZappers/BugStatusWorkFlow#CLOSED|CLOSED]] | ||
# A correct checksum must be published for each official release image | # A correct checksum must be published for each official release image [[QA:Testcase_Mediakit_ISO_Checksums]] | ||
# There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (DVD) install | # There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (DVD) install [[QA:Testcase_Mediakit_Repoclosure]] [[QA:Testcase_Mediakit_FileConflicts]] | ||
# Where platform support exists, all dedicated installer images (except {{filename|efidisk.img}}, which offers no options) must boot to the graphical boot menu and allow the user to select install options. If no option is selected, the installer should load after a reasonable timeout | # Where platform support exists, all dedicated installer images (except {{filename|efidisk.img}}, which offers no options) must boot to the graphical boot menu and allow the user to select install options. If no option is selected, the installer should load after a reasonable timeout [[QA:Testcase_Boot_Methods_Boot_Iso]] [[QA:Testcase_Boot_Methods_Dvd]] [[QA:Testcase_Live_Image_Boot]] | ||
# The installer must boot (if appropriate) and run on all [[Architectures#Primary_Architectures|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 an optical disc and when written to a USB stick with '''at least one''' of the [[How_to_create_and_use_Live_USB|officially supported methods]] | # The installer must boot (if appropriate) and run on all [[Architectures#Primary_Architectures|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 an optical disc and when written to a USB stick with '''at least one''' of the [[How_to_create_and_use_Live_USB|officially supported methods]] [[Test_Results:Fedora_18_Beta_TC6_Install?rd=Test_Results:Current_Installation_Test#USB_Stick]] <b>No explicit testcases for CD/DVD media, but most of the install testcases mention "either CD/DVD media or USB stick"</b> | ||
# The boot menu for all installation images should include an entry which causes both installation and the installed system to use a generic, highly compatible video driver (such as 'vesa'). This mechanism should work correctly, launching the installer and attempting to use the generic driver | # The boot menu for all installation images should include an entry which causes both installation and the installed system to use a generic, highly compatible video driver (such as 'vesa'). This mechanism should work correctly, launching the installer and attempting to use the generic driver [[QA:Testcase_Anaconda_User_Interface_Basic_Video_Driver]] <b>?</b> | ||
# The installer must be able to use at least one of the HTTP or FTP remote package source options | # The installer must be able to use at least one of the HTTP or FTP remote package source options [[QA:Testcase_install_repository_HTTP/FTP_graphical]] [[QA:Testcase_install_repository_HTTP/FTP_variation]] | ||
# When booting from a DVD ISO image, the installer must be able to use the DVD local package source options | # When booting from a DVD ISO image, the installer must be able to use the DVD local package source options [[QA:Testcase_install_repository_DVD_default]] | ||
# The installer must be able to complete an installation using the text, graphical and VNC installation interfaces | # The installer must be able to complete an installation using the text, graphical and VNC installation interfaces [[QA:Testcase_Anaconda_User_Interface_Graphical]] [[QA:Testcase_Anaconda_User_Interface_Text]] [[QA:Testcase_Anaconda_User_Interface_VNC]] [[QA:Testcase_Anaconda_User_Interface_VNC_Vncconnect]] [[QA:Testcase_Anaconda_User_Interface_VNC_Password]] | ||
# The installer must be able to install each of the release blocking desktops, as well as the minimal package set, with each supported installation method | # <b>!!</b>The installer must be able to install each of the release blocking desktops, as well as the minimal package set, with each supported installation method [[QA:Testcase_Package_Sets_Minimal_Package_Install]] <b>IMHO no testcases for desktops</b> | ||
# The installer must be able to complete an installation using any locally connected storage interface (e.g. PATA, SATA, SCSI etc...) with the default file system | # The installer must be able to complete an installation using any locally connected storage interface (e.g. PATA, SATA, SCSI etc...) with the default file system [[QA:Testcase_install_to_SATA_device]] [[QA:Testcase_install_to_PATA_device]] [[QA:Testcase_install_to_SCSI_device]] | ||
# The installer must be able to complete an installation using automatic partitioning to any sufficiently large target disk, whether unformatted, empty, or containing any kind of existing data | # The installer must be able to complete an installation using automatic partitioning to any sufficiently large target disk, whether unformatted, empty, or containing any kind of existing data [[QA:Testcase_anaconda_ext4_rootfs_on_disk_partition]] [[QA:Testcase_Anaconda_autopart_%28use_free_space%29_install]] [[QA:Testcase_Anaconda_autopart_%28shrink%29_install]] [[QA:Testcase_Anaconda_autopart_%28use_all_space%29_install]] [[QA:Testcase_Anaconda_autopart_%28encrypted%29_install]] [[QA:Testcase_Anaconda_autopart_install]] | ||
# <b>!!</b>The installer must allow the user to select which of the disks connected to the system will be affected by the installation process. Disks not selected as installation targets must not be affected by the installation process in any way <b>IMHO the same testcases as ^^, but none of them requires, that disks not selected must not be affected</b> | # <b>!!</b>The installer must allow the user to select which of the disks connected to the system will be affected by the installation process. Disks not selected as installation targets must not be affected by the installation process in any way <b>IMHO the same testcases as ^^, but none of them requires, that disks not selected must not be affected</b> | ||
# The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation | # The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation [[QA:Testcase_Anaconda_rescue_mode]] | ||
# The installer must be able to download and use an [[Anaconda/Updates| installer update image]] from an HTTP server | # The installer must be able to download and use an [[Anaconda/Updates| installer update image]] from an HTTP server [[QA:Testcase_Anaconda_updates.img_via_URL]] | ||
# The installer must be able to report failures to Bugzilla and local disk, with appropriate information included | # The installer must be able to report failures to Bugzilla and local disk, with appropriate information included [[QA:Testcase_Anaconda_save_traceback_to_bugzilla]] | ||
# In most cases (see [[Blocker_Bug_FAQ]]), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account | # In most cases (see [[Blocker_Bug_FAQ]]), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account [[QA:Testcase_base_firstboot]] | ||
# Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied | # Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied [[QA:Testcase_base_startup]] | ||
# <b>??</b>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 boot to a state where it is possible to log in through at least one of the default virtual consoles <b>maybe we'd like to add some specific one like | # <b>??</b>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 boot to a state where it is possible to log in through at least one of the default virtual consoles <b>maybe we'd like to add some specific one like [[QA:Testcase_base_startup]] seems to be for graphical startup</b> | ||
# It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments. The web browser must be able to download files, load extensions, and log into [https://admin.fedoraproject.org/accounts/ FAS] | # It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments. The web browser must be able to download files, load extensions, and log into [https://admin.fedoraproject.org/accounts/ FAS] [[QA:Testcase_desktop_browser]] | ||
# The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops | # The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops [[QA:Testcase_desktop_updates]] | ||
# <b>??</b> The default desktop background must be different from that of the two previous stable releases <b>IMHO no testcase coveres this, even though some testcases mention 'propper artwork for beta/final' | # <b>??</b> The default desktop background must be different from that of the two previous stable releases <b>IMHO no testcase coveres this, even though some testcases mention 'propper artwork for beta/final' [[QA:Testcase_Anaconda_User_Interface_Graphical]] [[QA:Testcase_base_startup</b>]] | ||
# <b>??</b>Any component which prominently identifies a Fedora release version number, code name or phase (Alpha, Beta, Final) must do so correctly <b>See ^^</b> | # <b>??</b>Any component which prominently identifies a Fedora release version number, code name or phase (Alpha, Beta, Final) must do so correctly <b>See ^^</b> | ||
# A system logging infrastructure must be available and enabled by default. It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages. This must be done in accordance with relevant standards accepted by the Project | # A system logging infrastructure must be available and enabled by default. It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages. This must be done in accordance with relevant standards accepted by the Project [[QA:Testcase_base_system_logging]] | ||
# <b>!!</b>It must be possible to trigger a system shutdown using standard console commands, and the system must shut down in such a way that storage volumes (e.g. simple partitions, LVs and PVs, RAID arrays) are taken offline safely and the system's BIOS or EFI is correctly requested to power down the system <b>IMHO no testcase coveres this</b> | # <b>!!</b>It must be possible to trigger a system shutdown using standard console commands, and the system must shut down in such a way that storage volumes (e.g. simple partitions, LVs and PVs, RAID arrays) are taken offline safely and the system's BIOS or EFI is correctly requested to power down the system <b>IMHO no testcase coveres this</b> | ||
Latest revision as of 10:51, 25 October 2012
- All bugs blocking the Alpha tracker must be CLOSED
- A correct checksum must be published for each official release image QA:Testcase_Mediakit_ISO_Checksums
- There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (DVD) install QA:Testcase_Mediakit_Repoclosure QA:Testcase_Mediakit_FileConflicts
- Where platform support exists, all dedicated installer images (except
efidisk.img, which offers no options) must boot to the graphical boot menu and allow the user to select install options. If no option is selected, the installer should load after a reasonable timeout QA:Testcase_Boot_Methods_Boot_Iso QA:Testcase_Boot_Methods_Dvd QA:Testcase_Live_Image_Boot - 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 an optical disc and when written to a USB stick with at least one of the officially supported methods Test_Results:Fedora_18_Beta_TC6_Install?rd=Test_Results:Current_Installation_Test#USB_Stick No explicit testcases for CD/DVD media, but most of the install testcases mention "either CD/DVD media or USB stick"
- The boot menu for all installation images should include an entry which causes both installation and the installed system to use a generic, highly compatible video driver (such as 'vesa'). This mechanism should work correctly, launching the installer and attempting to use the generic driver QA:Testcase_Anaconda_User_Interface_Basic_Video_Driver ?
- The installer must be able to use at least one of the HTTP or FTP remote package source options QA:Testcase_install_repository_HTTP/FTP_graphical QA:Testcase_install_repository_HTTP/FTP_variation
- When booting from a DVD ISO image, the installer must be able to use the DVD local package source options QA:Testcase_install_repository_DVD_default
- The installer must be able to complete an installation using the text, graphical and VNC installation interfaces QA:Testcase_Anaconda_User_Interface_Graphical QA:Testcase_Anaconda_User_Interface_Text QA:Testcase_Anaconda_User_Interface_VNC QA:Testcase_Anaconda_User_Interface_VNC_Vncconnect QA:Testcase_Anaconda_User_Interface_VNC_Password
- !!The installer must be able to install each of the release blocking desktops, as well as the minimal package set, with each supported installation method QA:Testcase_Package_Sets_Minimal_Package_Install IMHO no testcases for desktops
- The installer must be able to complete an installation using any locally connected storage interface (e.g. PATA, SATA, SCSI etc...) with the default file system QA:Testcase_install_to_SATA_device QA:Testcase_install_to_PATA_device QA:Testcase_install_to_SCSI_device
- The installer must be able to complete an installation using automatic partitioning to any sufficiently large target disk, whether unformatted, empty, or containing any kind of existing data QA:Testcase_anaconda_ext4_rootfs_on_disk_partition QA:Testcase_Anaconda_autopart_(use_free_space)_install QA:Testcase_Anaconda_autopart_(shrink)_install QA:Testcase_Anaconda_autopart_(use_all_space)_install QA:Testcase_Anaconda_autopart_(encrypted)_install QA:Testcase_Anaconda_autopart_install
- !!The installer must allow the user to select which of the disks connected to the system will be affected by the installation process. Disks not selected as installation targets must not be affected by the installation process in any way IMHO the same testcases as ^^, but none of them requires, that disks not selected must not be affected
- The rescue mode of the installer must start successfully and be able to detect and mount an existing default installation QA:Testcase_Anaconda_rescue_mode
- The installer must be able to download and use an installer update image from an HTTP server QA:Testcase_Anaconda_updates.img_via_URL
- The installer must be able to report failures to Bugzilla and local disk, with appropriate information included QA:Testcase_Anaconda_save_traceback_to_bugzilla
- In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account QA:Testcase_base_firstboot
- Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied QA:Testcase_base_startup
- ??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 boot to a state where it is possible to log in through at least one of the default virtual consoles maybe we'd like to add some specific one like QA:Testcase_base_startup seems to be for graphical startup
- It must be possible to run the default web browser and a terminal application from all release-blocking desktop environments. The web browser must be able to download files, load extensions, and log into FAS QA:Testcase_desktop_browser
- The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops QA:Testcase_desktop_updates
- ?? The default desktop background must be different from that of the two previous stable releases IMHO no testcase coveres this, even though some testcases mention 'propper artwork for beta/final' QA:Testcase_Anaconda_User_Interface_Graphical [[QA:Testcase_base_startup]]
- ??Any component which prominently identifies a Fedora release version number, code name or phase (Alpha, Beta, Final) must do so correctly See ^^
- A system logging infrastructure must be available and enabled by default. It must provide at least basic local file-based logging of kernel messages, and allow other components to write log messages. This must be done in accordance with relevant standards accepted by the Project QA:Testcase_base_system_logging
- !!It must be possible to trigger a system shutdown using standard console commands, and the system must shut down in such a way that storage volumes (e.g. simple partitions, LVs and PVs, RAID arrays) are taken offline safely and the system's BIOS or EFI is correctly requested to power down the system IMHO no testcase coveres this