From Fedora Project Wiki
(Created page with "{{Template:Associated_release_criterion|Beta|custom-partitioning}} {{QA/Test_Case |description=This test case tests the installer's ability to use custom partitioning. |actio...")
 
No edit summary
Line 11: Line 11:
# Proceed with the installation
# Proceed with the installation
|results=
|results=
# Anaconda should succesfully create, destroy and assign mount points to partitions of any specified size using most commonly-used filesystem types
# Anaconda should successfully create, destroy and assign mount points to partitions of any specified size using most commonly-used filesystem types
# Anaconda should reject obviously invalid operations without crashing
# Anaconda should reject obviously invalid operations without crashing
# The system should install successfully
# The system should install successfully

Revision as of 15:39, 3 December 2013

Note.png
Associated release criterion
This test case is associated with the Fedora_41_Beta_Release_Criteria#custom-partitioning 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 case tests the installer's ability to use custom partitioning.


How to test

  1. Boot the installer using any available means
  2. In Installation destination select the appropriate disk (or disks)
  3. In Installation option choose I want to review/modify my disk partitions befor continuing
  4. Make sure your disk is not set to be encrypted
  5. Use the custom partitioning screen to create disk layout
  6. Proceed with the installation

Expected Results

  1. Anaconda should successfully create, destroy and assign mount points to partitions of any specified size using most commonly-used filesystem types
  2. Anaconda should reject obviously invalid operations without crashing
  3. The system should install successfully
  4. After install, the system initiates boot properly