From Fedora Project Wiki

(add the 'associated criterion' block)
(update a bit, Productize as DVDs don't really exist any more (name change coming))
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Alpha_Release_Criteria#Release-blocking_images_must_boot}}
{{Template:Associated_release_criterion|Alpha|initialization-requirements}}


{{QA/Test_Case
{{QA/Test_Case
|description=This test verifies that {{filename|DVD.iso}} image can be booted and installed from a USB stick created by a {{command|livecd-iso-to-disk}} command.
|description=This test verifies that a traditional installer image containing packages can be booted and installed from a USB stick created by a {{command|livecd-iso-to-disk}} command.
{{admon/warning|You might lose your data|This test case requires you to use low-level system utilities that can easily destroy all your data when used incorrectly. Only follow this if you are a highly-experienced user or you don't mind losing your system and your data.}}
{{admon/warning|Data loss|Any data on the USB stick used for this test is likely to be destroyed. Please do not use a stick whose contents you need to keep.}}
|setup=
|setup=
# You need to have a USB stick that is larger than the {{filename|DVD.iso}} image.
# Download the image you wish to test. This must be a traditional (i.e. non-live) installer-based image containing a package repository, such as the [[Server]] offline install image.
# Install {{package|livecd-tools}}.
# Ensure you have a USB stick that is larger than the live image whose contents you can afford to lose (the contents of the stick will be destroyed as a part of the test).
# On an existing Fedora system, install {{package|livecd-tools}}.
|actions=
|actions=
# Convert the {{filename|DVD.iso}} image to the USB stick using {{command|livecd-iso-to-disk}}.
# Write the image to the USB stick using {{command|livecd-iso-to-disk}}.
#* Example command is: {{#tag:pre|# livecd-iso-to-disk --format --reset-mbr Fedora-{{FedoraVersionNumber|next}}-x86_64-DVD.iso /dev/sdX}} where you replace ''sdX'' by your USB stick device identifier. '''This will destroy all data on that disk.'''
#* Example command is: {{#tag:pre|# livecd-iso-to-disk --format --reset-mbr --efi Fedora-{{FedoraVersionNumber|next}}-x86_64-DVD.iso /dev/sdX}} where you replace ''sdX'' by your USB stick device identifier. '''This will destroy all data on that disk.'''
#* If you need to test [[How_to_create_and_use_Live_USB#UEFI_boot_of_USB_sticks|UEFI boot]], you need to add {{command|--efi}} option.
#* A longer guide how to use this command is available at [[How to create and use Live USB#Using the livecd-iso-to-disk tool]]. You can also run the command with {{command|--help}} option.
#* A longer guide how to use this command is available at [[How to create and use Live USB#Using the livecd-iso-to-disk tool]]. You can also run the command with {{command|--help}} option.
# Boot the system from the USB stick.
# Boot the system from the USB stick.
# Proceed with the installation.
# Proceed with the installation.
|results=
|results=
# The ISO image is converted to the USB stick without error.
# The image is written to the USB stick without error.
# The DVD image boots into the installer without error.
# The USB stick boots into the installer without error.
# The installation finishes successfully.
# The installation finishes successfully, and uses the package repository on the USB stick (not a network repository).
# The new system initiates boot properly.
# The new system initiates boot properly. Note that problems after boot that do not seem to be related to writing the image to a USB stick are likely out of the scope of this test case, though they may count as failures of one of the other installation validation test cases.
}}
}}


[[Category:Installer Boot Methods]]
[[Category:Installer Boot Methods]]
[[Category:USB_test_cases]]

Revision as of 23:48, 8 July 2014

Note.png
Associated release criterion
This test case is associated with the Basic_Release_Criteria#initialization-requirements release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


Description

This test verifies that a traditional installer image containing packages can be booted and installed from a USB stick created by a livecd-iso-to-disk command.

Warning.png
Data loss
Any data on the USB stick used for this test is likely to be destroyed. Please do not use a stick whose contents you need to keep.

Setup

  1. Download the image you wish to test. This must be a traditional (i.e. non-live) installer-based image containing a package repository, such as the Server offline install image.
  2. Ensure you have a USB stick that is larger than the live image whose contents you can afford to lose (the contents of the stick will be destroyed as a part of the test).
  3. On an existing Fedora system, install Package-x-generic-16.pnglivecd-tools.

How to test

  1. Write the image to the USB stick using livecd-iso-to-disk.
    • Example command is:
      # livecd-iso-to-disk --format --reset-mbr --efi Fedora-40-x86_64-DVD.iso /dev/sdX
      where you replace sdX by your USB stick device identifier. This will destroy all data on that disk.
    • A longer guide how to use this command is available at How to create and use Live USB#Using the livecd-iso-to-disk tool. You can also run the command with --help option.
  2. Boot the system from the USB stick.
  3. Proceed with the installation.

Expected Results

  1. The image is written to the USB stick without error.
  2. The USB stick boots into the installer without error.
  3. The installation finishes successfully, and uses the package repository on the USB stick (not a network repository).
  4. The new system initiates boot properly. Note that problems after boot that do not seem to be related to writing the image to a USB stick are likely out of the scope of this test case, though they may count as failures of one of the other installation validation test cases.