From Fedora Project Wiki

(adjust associated_release_criterion template invocation)
(link to Testcase_Anaconda_updates.img_via_URL for a prepared updates.img, improve formatting and instructions)
 
Line 2: Line 2:
  
 
{{QA/Test_Case
 
{{QA/Test_Case
|description=This test will verify that anaconda can load an {{filename|updates.img}} from removable media.  Note, this test needs removable media for storing an {{filename|updates.img}} (USB storage or floppy disk). Additional information on using an {{filename|updates.img}} can be found at [[Anaconda/Updates]].
+
|description=This test will verify that anaconda can load an {{filename|updates.img}} from removable media.  Note, this test needs removable media for storing an {{filename|updates.img}} (usually USB storage).
 +
|setup=
 +
# Prepare a valid {{filename|updates.img}} file. There is an {{filename|updates.img}} prepared for you in [[QA:Testcase Anaconda updates.img via URL|this test case]]. You can use it and follow the same steps to verify that it is applied. If it doesn't work or you want to use a different one, see [[Anaconda/Updates#create-images|this page]] for image creation instructions, and prepare your own file. A good thing to change in the image is the ''What language would you like to use during the installation process?'' text in {{filename|pyanaconda/ui/gui/spokes/welcome.glade}}, as this text is displayed on one of the first screens.
 +
# Copy the {{filename|updates.img}} to your removable media
 
|actions=
 
|actions=
# Prepare a valid {{filename|updates.img}} file. See [[Anaconda/Updates#create-images|this page]] for image creation instructions. A good thing to change in the {{filename|updates.img}} is the "What language would you like to use during the installation process?" text in {{filename|pyanaconda/ui/gui/spokes/welcome.glade}}, as this text is displayed on one of the first screens.
+
# Insert the removable drive (usually a USB key)
# Copy the {{filename|updates.img}} to your removable media
+
# Boot the installer with the boot argument: <pre>inst.updates=hd:LABEL=label:/updates.img</pre> or <pre>inst.updates=hd:UUID=uuid:/updates.img</pre> where <code>label</code> is the label of the partition or <code>uuid</code> is its UUID. So if the stick had the label <code>KINGSTON</code>, you'd put <pre>inst.updates=hd:LABEL=KINGSTON:/updates.img</pre>  See [[Anaconda Boot Options]] for information on supported boot options.
# Insert the removable drive (USB key or floppy disk)
+
# If it's possible, visually identify that the update was applied. If you have used the prepared {{filename|updates.img}} from [[QA:Testcase Anaconda updates.img via URL|this test case]], follow its relevant steps to verify it applied correctly.
# Boot the installer with the boot argument: <code>updates=hd:LABEL=(label):/updates.img</code> or <code>updates=hd:UUID=(UUID):/updates.img</code>, where label is the label of the partition or UUID is its UUID (so if the stick had the label KINGSTON, you'd put <code>updates=hd:LABEL=KINGSTON:/updates.img</code>
+
# If it's not visually possible to confirm the update was applied (there were just code changes), verify the existence of {{filename|/tmp/updates}} directory, which should contain all updated source code files.
 +
# Proceed with installation
 
|results=
 
|results=
# Anaconda prepares the {{filename|updates.img}} and copies its content to {{filename|/tmp/updates/}}. Any changes you included in the updates.img file are applied
+
# Anaconda downloads the {{filename|updates.img}} and copies its content to {{filename|/tmp/updates/}}. Any changes you included in the updates.img file are applied (image changes, text adjustments, source code changes, etc).
 
# Anaconda proceeds without related errors
 
# Anaconda proceeds without related errors
 
}}
 
}}
  
 
[[Category:Recovery Test Cases]]
 
[[Category:Recovery Test Cases]]

Latest revision as of 13:34, 11 November 2014

Note.png
Associated release criterion
This test case is associated with the Fedora_34_Final_Release_Criteria#update-image 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 will verify that anaconda can load an updates.img from removable media. Note, this test needs removable media for storing an updates.img (usually USB storage).

Setup

  1. Prepare a valid updates.img file. There is an updates.img prepared for you in this test case. You can use it and follow the same steps to verify that it is applied. If it doesn't work or you want to use a different one, see this page for image creation instructions, and prepare your own file. A good thing to change in the image is the What language would you like to use during the installation process? text in pyanaconda/ui/gui/spokes/welcome.glade, as this text is displayed on one of the first screens.
  2. Copy the updates.img to your removable media

How to test

  1. Insert the removable drive (usually a USB key)
  2. Boot the installer with the boot argument:
    inst.updates=hd:LABEL=label:/updates.img
    or
    inst.updates=hd:UUID=uuid:/updates.img
    where label is the label of the partition or uuid is its UUID. So if the stick had the label KINGSTON, you'd put
    inst.updates=hd:LABEL=KINGSTON:/updates.img
    See Anaconda Boot Options for information on supported boot options.
  3. If it's possible, visually identify that the update was applied. If you have used the prepared updates.img from this test case, follow its relevant steps to verify it applied correctly.
  4. If it's not visually possible to confirm the update was applied (there were just code changes), verify the existence of /tmp/updates directory, which should contain all updated source code files.
  5. Proceed with installation

Expected Results

  1. Anaconda downloads the updates.img and copies its content to /tmp/updates/. Any changes you included in the updates.img file are applied (image changes, text adjustments, source code changes, etc).
  2. Anaconda proceeds without related errors