From Fedora Project Wiki

m (add autolang to page)
(add the 'associated criterion' block)
Line 1: Line 1:
{{autolang|base=yes}}
{{autolang|base=yes}}
{{Template:Associated_release_criterion|releasecriterion=Fedora_{{FedoraVersionNumber|next}}_Final_Release_Criteria#Desktop_keyring}}


{{QA/Test_Case
{{QA/Test_Case

Revision as of 23:27, 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.


Description

This test case tests whether a desktop environment can store and retrieve passwords (keyring functionality).


How to test

  1. Clean boot the Fedora you wish to test: this could be a system installed from a particular snapshot, pre-release, or release, or a live image
  2. Perform an action which should result in a password being stored in a keyring. Common examples would be setting up an account in the desktop's native email client, connecting to an encrypted wireless network, or using a passphrase-protected SSH key in some way, for instance by logging in to a remote system via SSH
  3. If offered the choice, agree to store the password / passphrase for future re-use
  4. Attempt the same operation again, and observe whether the stored password or passphrase is re-used, or offered for re-use
  5. If testing an installed system, restart the system and test the operation again to see if the stored password or passphrase is re-used, or offered for re-use

Expected Results

  1. The desktop should offer to store passwords or passphrases entered into compatible applications
  2. The desktop should correctly re-use or offer to re-use (depending on configuration and desktop default behaviour) the stored passwords or passphrases when appropriate