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}}_Alpha_Release_Criteria#Required_applications}} | |||
{{QA/Test_Case | {{QA/Test_Case | ||
Revision as of 22:54, 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 the default web browser is operational in a given installation.
How to test
- 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
- Try to launch the default web browser in a typical way for the tested desktop environment: for instance, from the system menus, or by clicking on an icon in the panel
- If your first tried method fails, note the reason why, and try a different method of launching the browser; continue to note any other failures you experience
- Once you have managed to launch the browser, attempt to log in to FAS (the Fedora Accounts System) with a valid Fedora project account
- Attempt to download a file from any typical web server - for instance, visit the Linux kernel site and attempt to download the latest stable kernel release tarball
- If appropriate for the browser under test, attempt to install and use a commonly-used Mozilla-type extension, such as AdBlock Plus. If this fails, note the characteristics of the failure, and try another extension. If the browser supports a different, commonly-used extension system, test enabling an extension of that type instead
Expected Results
- It should be possible to launch the browser by any typically-used method for the desktop tested
- The browser should be capable of connecting to and correctly displaying the FAS page, and handling the login process
- The browser should download the requested file to the default
Downloadsdirectory - The browser should be capable of using extensions correctly