From Fedora Project Wiki

Revision as of 21:55, 19 January 2009 by Jkeating (talk | contribs)

Warning.png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
EDITING IN PROGRESS, HANG ON THERE YOUNGSTER

This page is intended to record Fedora 11 Installation test results for the Alpha milestone.

If you would like to suggest a test case to add to this page, please don't hesitate to do so, or send questions to fedora-test-list.

Instructions

  1. Select a test case.
  2. Fill in which architecture you tested: i686, x86_64 or ppc.
  3. Fill in a testresult template with your wiki username, as shown in the Key section.
  4. If a failure occurs, fill in the appropriate bug number using the form.

Notes

Key

Please use the following format when posting results to this page

Example Explanation
Untested
USERNAME Indicates an inprogress or test that needs further review
USERNAME Indicates a test that has passed
USERNAME Indicates a failed test ... see Notes/Bug(s) for details

Boot Methods

Test Case Architectures Bug(s)
i386 ppc x86_64
QA/TestCases/BootMethodsBootIso jkeating
QA/TestCases/BootMethodsCdrom
QA/TestCases/BootMethodsDvd jkeating
QA/TestCases/BootMethodsUsb
QA/TestCases/BootMethodsNetboot
QA/TestCases/BootMethodsPxeboot jkeating jkeating
QA/TestCases/BootMethodsXenParaVirt
QA/TestCases/BootMethodsKVM jkeating jkeating
QA/TestCases/BootMethodsRescueMode

Installation Source

Test Case Architectures Bug(s)
i386 ppc x86_64
QA/TestCases/InstallSourceHttp jkeating jkeating
QA/TestCases/InstallSourceNfs jkeating jkeating
QA/TestCases/InstallSourceNfsIso jkeating
QA/TestCases/InstallSourceCdrom
QA/TestCases/InstallSourceDvd jkeating
QA/TestCases/InstallSourceFtpAnonymous
QA/TestCases/InstallSourceFtpNonAnonymous
QA/TestCases/InstallSourceHardDrive

Kickstart Delivery

Test Case Architectures Bug(s)
i386 ppc x86_64
QA/TestCases/KickstartKsFilePathKsCfg
QA/TestCases/KickstartKsHdDevicePathKsCfg
QA/TestCases/KickstartKsHttpServerKsCfg jkeating jkeating
QA/TestCases/KickstartKsNfsServerPathKsCfg

Package Sets

Test Case Architectures Bug(s)
i386 ppc x86_64
QA/TestCases/PackageSetsDefaultPackageInstall jkeating
QA/TestCases/PackageSetsMinimalPackageInstall jkeating
QA/TestCases/PackageSetsEverything

Partitioning

Test Case Architectures Bug(s)
i386 ppc x86_64
QA/TestCases/PartitioningExt3OnNativeDevice jkeating
QA/TestCases/PartitioningRootfsOnLvmDevice jkeating jkeating
QA/TestCases/PartitioningRootfsOnRaid1
QA/TestCases/PartitioningExt2OnNativeDevice
QA/TestCases/PartitioningNoSwap jkeating
QA/TestCases/PartitioningRaid0OnLvmDevice
QA/TestCases/PartitioningSwapOnLvmDevice jkeating jkeating
QA/TestCases/PartitioningUninitializedDisks
QA/TestCases/PartitioningUsrOnRaid0
QA/TestCases/PartitioningUsrOnRaid5
QA/TestCases/PartitioningUsrOnRaid6
QA/TestCases/PartitioningRootfsOnDmraidDevice
QA/TestCases/PartitioningPreExistingLvm2Lvm2 jkeating jkeating
QA/TestCases/PartitioningPreExistingRaidRaid
QA:Encrypted Root install test jkeating rhbug:480667 - Race for root mount fails without boot_delay=5. Unable to bring up lvm group and mount /

Recovery

Test Case Architectures Bug(s)
i386 ppc x86_64
QA/TestCases/UpdatesImgPrompt
QA/TestCases/UpdatesImgViaTree
QA/TestCases/UpdatesImgViaHttp
QA/TestCases/UpdatesImgViaUsb
QA/TestCases/TracebackSaveRemote
QA/TestCases/TracebackSaveToBugzilla
QA/TestCases/TracebackDebugMode

Storage Devices

Test Case Architectures Bug(s)
i386 ppc x86_64
QA/TestCases/StorageDeviceSata jkeating jkeating rhbug:480667 - Race for root mount fails without boot_delay=5. Unable to bring up lvm group and mount /
QA/TestCases/StorageDeviceScsi
QA/TestCases/StorageDeviceiScsi

User Interface

Test Case Architectures Bug(s)
i386 ppc x86_64
QA/TestCases/UserInterfaceGraphical jkeating
QA/TestCases/UserInterfaceText
QA/TestCases/UserInterfaceVnc
QA/TestCases/UserInterfaceCmdline
QA/TestCases/UserInterfaceTelnet

Origin

This page was created using QA:Fedora 11 Install Results Template as a template. Any changes to this page should also be made on the template so they are carried forward for the next release.