From Fedora Project Wiki

(add to relevant category)
(make release specification easier to read instead of overcomplicated)
 
(3 intermediate revisions by one other user not shown)
Line 8: Line 8:
 
|actions=
 
|actions=
 
{{admon/note|Test procedure|
 
{{admon/note|Test procedure|
* Throughout the following steps, look for any form of 'release identification' - e.g. text stating "Fedora", or "Fedora Server", or "Fedora {{FedoraVersionNumber|next}}", or "Fedora Alpha", or anything else along those lines. If you notice ''any'' case of ''incorrect'' identification, then this should be reported as a bug and as a failure of this test. When testing a Final release candidate, there should nothing that identifies the release as a pre-release of any kind.
+
* Throughout the following steps, look for any form of 'release identification' - e.g. text stating "Fedora", or "Fedora Server", or "Fedora {{FedoraVersionNumber|next}}", or "Fedora Beta", or anything else along those lines. If you notice ''any'' case of ''incorrect'' identification, then this should be reported as a bug and as a failure of this test. When testing a Final release candidate, there should nothing that identifies the release as a pre-release of any kind.
 
* Similarly, look out for everything that looks like Fedora-sourced 'artwork'. If you spot any artwork that is clearly associated with a ''different'' Fedora release - e.g. a desktop background from the previous release - this is likely a bug, and should be reported as such. If you are testing a Final release candidate, any artwork that implies or suggests the release is a pre-release is also likely a bug. If you encounter artwork you're not sure is correct or appropriate, please report this as a bug, and report the result of this test as 'warn'.}}
 
* Similarly, look out for everything that looks like Fedora-sourced 'artwork'. If you spot any artwork that is clearly associated with a ''different'' Fedora release - e.g. a desktop background from the previous release - this is likely a bug, and should be reported as such. If you are testing a Final release candidate, any artwork that implies or suggests the release is a pre-release is also likely a bug. If you encounter artwork you're not sure is correct or appropriate, please report this as a bug, and report the result of this test as 'warn'.}}
 
# Install or deploy the Fedora release you wish to test, with the desired package set. Set a root password, but do '''not''' create a standard user account during installation.
 
# Install or deploy the Fedora release you wish to test, with the desired package set. Set a root password, but do '''not''' create a standard user account during installation.
Line 18: Line 18:
 
|results=
 
|results=
 
# Any form of release identification that refers to a distribution name must state 'Fedora'.
 
# Any form of release identification that refers to a distribution name must state 'Fedora'.
# Any form of release identification that refers to a release phase / milestone (e.g. Alpha or Beta) must refer to the correct one. For Final composes, nothing may identify the release as a pre-release.
+
# Any form of release identification that refers to a release phase / milestone (e.g. Beta) must refer to the correct one. For Final composes, nothing may identify the release as a pre-release.
# Any form of release identification that refers to a flavor (''Server'', ''Workstation'', ''Cloud'' etc.) must refer to the correct one.
+
# Any form of release identification that refers to an [[Editions|Edition]] (''Server'', ''Workstation'', ''Atomic'' etc.) must refer to the correct one.
 
# Any form of release identification that refers to a release number must refer to the correct one.
 
# Any form of release identification that refers to a release number must refer to the correct one.
# If the release being tested is an Alpha or Beta pre-release build, the default desktop backgrounds from the previous two stable releases may not appear as the default desktop background (or login manager background, or 'first boot' utility background, or really anywhere).
+
# If the release being tested is a Beta pre-release or candidate compose, the default desktop backgrounds from the previous two stable releases may not appear as the default desktop background (or login manager background, or 'first boot' utility background, or really anywhere).
# If the release being tested is a final release or post-Beta pre-release build, the artwork used in the 'first boot' utility (if any), login manager (if any) and on the desktop (particularly the background) must be the correct and current artwork proposed for the release in question by the design team. If a background or artwork is used in the bootloader menu screen or the graphical boot process it must be either entirely generic (such as the Fedora logo) or part of the correct and current proposed artwork.
+
# If the release being tested is a Final pre-release or candidate compose, the artwork used in the 'first boot' utility (if any), login manager (if any) and on the desktop (particularly the background) must be the correct and current artwork proposed for the release in question by the design team. If a background or artwork is used in the bootloader menu screen or the graphical boot process it must be either entirely generic (such as the Fedora logo) or part of the correct and current proposed artwork.
 
}}
 
}}
  
 
[[Category:Base Acceptance Test Cases]]
 
[[Category:Base Acceptance Test Cases]]

Latest revision as of 11:12, 13 September 2018

Note.png
Associated release criterion
This test case is associated with the Basic_Release_Criteria#desktop-background 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 Basic_Release_Criteria#self-identification 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_32_Final_Release_Criteria#artwork 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 checks that appropriate artwork and release identification are in place throughout a typical deployment and boot of Fedora.

Note.png
Only artwork and release identification issues
Please note that this test case assumes the install and boot process works normally. If you encounter a different bug while running this test, please report it as a bug and report a failure for the most appropriate test case you can find in the matrices. If you are able to work around the bug and complete this test and discover no artwork or release identification issues, you may still report a 'pass' for this test. If the bug prevents you from fully completing this test, please report either a 'warn' or no result.


How to test

Note.png
Test procedure
  • Throughout the following steps, look for any form of 'release identification' - e.g. text stating "Fedora", or "Fedora Server", or "Fedora 32", or "Fedora Beta", or anything else along those lines. If you notice any case of incorrect identification, then this should be reported as a bug and as a failure of this test. When testing a Final release candidate, there should nothing that identifies the release as a pre-release of any kind.
  • Similarly, look out for everything that looks like Fedora-sourced 'artwork'. If you spot any artwork that is clearly associated with a different Fedora release - e.g. a desktop background from the previous release - this is likely a bug, and should be reported as such. If you are testing a Final release candidate, any artwork that implies or suggests the release is a pre-release is also likely a bug. If you encounter artwork you're not sure is correct or appropriate, please report this as a bug, and report the result of this test as 'warn'.
  1. Install or deploy the Fedora release you wish to test, with the desired package set. Set a root password, but do not create a standard user account during installation.
  2. Boot the installed system, observing any artwork and release identification that appear in the bootloader and during the boot process.
  3. If a 'first boot' utility runs, use it to create a user account, while observing any artwork and release identification.
  4. Observe any artwork and release identification at the login screen. Particularly, if doing a graphical install, check the background image. Log in as the created user account (if a 'first boot' tool ran) or as root (if not). Observe any artwork and release identification that appear during and immediately after login - again, if doing a graphical install, particularly check the desktop background.
  5. Check the contents of common release identification files, e.g. /etc/fedora-release and /etc/os-release.
  6. If doing a graphical install, check obvious places where release artwork and identification may be found, e.g. the control center Details pane on GNOME.

Expected Results

  1. Any form of release identification that refers to a distribution name must state 'Fedora'.
  2. Any form of release identification that refers to a release phase / milestone (e.g. Beta) must refer to the correct one. For Final composes, nothing may identify the release as a pre-release.
  3. Any form of release identification that refers to an Edition (Server, Workstation, Atomic etc.) must refer to the correct one.
  4. Any form of release identification that refers to a release number must refer to the correct one.
  5. If the release being tested is a Beta pre-release or candidate compose, the default desktop backgrounds from the previous two stable releases may not appear as the default desktop background (or login manager background, or 'first boot' utility background, or really anywhere).
  6. If the release being tested is a Final pre-release or candidate compose, the artwork used in the 'first boot' utility (if any), login manager (if any) and on the desktop (particularly the background) must be the correct and current artwork proposed for the release in question by the design team. If a background or artwork is used in the bootloader menu screen or the graphical boot process it must be either entirely generic (such as the Fedora logo) or part of the correct and current proposed artwork.