From Fedora Project Wiki

Note.png
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.
Note.png
Associated release criterion
This test case is associated with the Fedora_34_Final_Release_Criteria#default-application-functionality 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 tests basic functionality of a selected desktop application (specified in a release validation matrix or some other place from which this test case was linked).

Setup

  1. Perform a standard installation of the Fedora version you wish to test. It must be include a desktop environment.
  2. If your task is not to check a concrete application, but a primary/default application of a specified application type (e.g. a default image viewer, a default text editor, etc), you first need to have a look whether the desktop environment contains just a single or multiple applications of this type. If there is just one, that's the one you need to test. If there are multiple, figure out what the default application is. The usual way is to look into system configuration (e.g. gnome-control-center -> Default Applications), or to launch the default application on an appropriate file type (e.g. double click on an .odt file in a file manager), or to look into a favorites menu section (e.g. KDE menu -> Favorites).
    • If the primary/default application can't be determined, start testing all applications of the given application type. Once you find any application that passes this test case, you can finish your testing, finding a single such application is satisfactory. When reporting results, state which application it is. Report all problems found in that one and other tested applications.

How to test

  1. Launch the selected application from a graphical menu, the same way an end-user would launch it.
  2. Try basic usage of the application (calculating numbers in a calculator, displaying images in an image viewer, playing music in a music player, etc).
    • The application must at least be broadly capable of its most basic expected operations, and it must not crash without user intervention or with only basic user intervention.
  3. If the application is supposed to be associated with some file types, try opening the application on such a file from a file manager (e.g. open the image viewer by clicking on a .png file).
    • The application should open (either by default, or when selected from an application list, according to your expectation) and display the content.
  4. If the application supports saving files as its main function (e.g. a text editor, a graphics editor, etc), try to create some example content, save it to a file, close the application, and then reopen it in the application again.
    • The content should look exactly the same after reopening.

Expected Results

  1. All expectations mentioned in the How to test section are met.