From Fedora Project Wiki
No edit summary |
(add the 'associated criterion' block) |
||
| Line 1: | Line 1: | ||
{{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Beta_Release_Criteria#Guided_partitioning}} | |||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This test case tests whether installing using encryption using the anaconda recommended defaults functions properly. | |description=This test case tests whether installing using encryption using the anaconda recommended defaults functions properly. | ||
Revision as of 23:03, 25 July 2013
Associated release criterion
This test case is associated with the Fedora_42_MILESTONE_Release_Criteria#CRITERION_NAME 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.
This test case is associated with the Fedora_42_MILESTONE_Release_Criteria#CRITERION_NAME 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 whether installing using encryption using the anaconda recommended defaults functions properly.
Other paths
Make sure to also test other installation paths, like QA:Testcase_Anaconda_custom_partitioning, QA:Testcase_Anaconda_autopart_(shrink)_install and others, with the encryption enabled.
Make sure to also test other installation paths, like QA:Testcase_Anaconda_custom_partitioning, QA:Testcase_Anaconda_autopart_(shrink)_install and others, with the encryption enabled.
Setup
- Start with a disk containing no partitions
How to test
- Boot the installer using any available means
- Make sure your disk is set to be encrypted
- you can encrypt the whole disk before custom partitioning your disk
- or encrypt part of the disk (for example,/root) after custom partitioning your disk
- Select the appropriate disk, and continue installation, choosing all provided defaults
- Continue installation with choosing all provided defaults
- After installation is complete, perform QA:Testcase_base_startup to ensure the installed system boots correctly with the encrypted partition
- Repeat the test, selecting a non-English keyboard map and entering a passphrase which would not be input the same on an English keyboard map
Some keyboard layouts might be problematic
Some keyboard layouts differ in graphical environment and in console. Therefore it might happen that the exact password used in Anaconda to encrypt the disk might not work in Plymouth to unlock the disk. That is documented in RHBZ #743281 and we currently have no solution for it. Hitting Pause key before entering the password to unlock the disk might help in some cases to switch to a correct layout, e.g. this helps for the Czech qwerty (cz-lat2) layout.
Some keyboard layouts differ in graphical environment and in console. Therefore it might happen that the exact password used in Anaconda to encrypt the disk might not work in Plymouth to unlock the disk. That is documented in RHBZ #743281 and we currently have no solution for it. Hitting Pause key before entering the password to unlock the disk might help in some cases to switch to a correct layout, e.g. this helps for the Czech qwerty (cz-lat2) layout.
Expected Results
- The system should install successfully
- After install, the system initiates boot properly and partitions can be unlocked
Follow-up testing
Testing that the installed system boots correctly is part of QA:Testcase_base_startup. Please perform that test after this one in order to ensure the system correctly unlocks the encrypted partition on boot. Failures after the installation stage should be recorded as a failure in that test case, not this one.
Testing that the installed system boots correctly is part of QA:Testcase_base_startup. Please perform that test after this one in order to ensure the system correctly unlocks the encrypted partition on boot. Failures after the installation stage should be recorded as a failure in that test case, not this one.