From Fedora Project Wiki

m (add autolang to page)
mNo edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{autolang|base=yes}}
{{autolang|base=yes}}
{{Template:Associated_release_criterion|Alpha|required-applications}}


{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests whether the default web browser is operational in a given installation.
|description=This test case tests whether the default web browser is operational in a given installation.
|actions=
|actions=
# 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
# 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
# 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
# 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 [https://admin.fedoraproject.org/accounts/ FAS (the Fedora Accounts System)] with a valid Fedora project account
# Once you have managed to launch the browser, attempt to log in to [https://admin.fedoraproject.org/accounts/ 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 [http://www.kernel.org/ Linux kernel site] and attempt to download the latest stable kernel release tarball
# Attempt to download a file from any typical web server - for instance, visit the [http://www.kernel.org/ 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 [http://adblockplus.org/ 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
# If appropriate for the browser under test, attempt to install and use a commonly-used Mozilla-type extension, such as [http://adblockplus.org/ 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.
 
|results=
|results=
# It should be possible to launch the browser by any typically-used method for the desktop tested
# 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 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 {{filename|Downloads}} directory
# The browser should download the requested file to the default {{filename|Downloads}} directory.
# The browser should be capable of using extensions correctly
# The browser should be capable of using extensions correctly.
}}
}}
[[Category:Desktop_Acceptance_Test_Cases]]
[[Category:Desktop_Acceptance_Test_Cases]]

Latest revision as of 08:30, 28 September 2017

Associated release criterion
This test case is associated with the Basic_Release_Criteria#required-applications 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

  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. 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.
  3. 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.
  4. Once you have managed to launch the browser, attempt to log in to FAS (the Fedora Accounts System) with a valid Fedora project account.
  5. 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.
  6. 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

  1. It should be possible to launch the browser by any typically-used method for the desktop tested.
  2. The browser should be capable of connecting to and correctly displaying the FAS page, and handling the login process.
  3. The browser should download the requested file to the default Downloads directory.
  4. The browser should be capable of using extensions correctly.
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_desktop_browser&oldid=502382"