From Fedora Project Wiki

No longer current
The compose for which this page contains results is no longer the current one. This page contains the results for the current compose.

This page records Security Lab validation testing test results for the Fedora 25 20160927.n.0 nightly compose.

Which tests to run[edit]

Test coverage page
Lab.html This page provides information about test coverage for the tests on this page across all the composes for the current release: it can help you see which test cases most need to be run.

Tests with a Milestone of Basic, Beta or Final are the most important. Optional tests are less so, but still useful to run. The milestone indicates that for that milestone release or a later one to be approved for release, the test must have been run against the release candidate build (so at Beta, all Basic and Beta tests must have been run, for instance). However, it is important to run the tests for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not been run at all, or not run recently, for the current release.

How to test[edit]

1. Download one or more media for testing:

Image armhfp i386 x86_64
Everything boot Download Download
Workstation boot Download Download
Workstation live Download Download
Server dvd Download Download Download
Server boot Download Download
Cloud boot Download Download
Cloud_Base vagrant-libvirt Download
Atomic vagrant-libvirt Download
Cloud_Base vagrant-virtualbox Download
Cloud_Base raw-xz Download
Atomic vagrant-virtualbox Download
Atomic qcow2 Download
Atomic boot Download
Cloud_Base qcow2 Download
Docker_Base docker Download Download
Atomic raw-xz Download
KDE live Download Download
SoaS live Download Download
LXDE live Download Download
Design_suite live Download Download
Jam_KDE live Download Download
Astronomy_KDE live Download Download
Robotics live Download Download
Scientific_KDE live Download Download
Workstation raw-xz Download
Server raw-xz Download
KDE raw-xz Download
Minimal raw-xz Download
SoaS raw-xz Download
LXDE raw-xz Download

2. Perform one or more of the test cases and add your results to the table below

  • You can submit results by editing the page directly, or by using relval, with the relval report-results command. It provides a simple text interface for reporting test results.

3. If a test fails, file a bug report. You may propose the bug as a release blocker or freeze exception bug for the appropriate release - see blocker bug process and freeze exception bug process.

Some tests must be run against particular Products or images - for example, the #Default boot and install tests. If no particular product or image is specified either in this page or the test case page, you can use any appropriate image. For example, you can run most of the #General Tests with the Workstation live image, or either of the Server install images.

If you notice a problem during a test which does not constitute a complete failure of the test, you should still file a bug report, but it may not be appropriate to propose it as a release blocker bug. Use your judgment in deciding this, with reference to the Fedora_Release_Criteria, which these tests are intended to verify. If you are unsure, err on the side of proposing the bug as a blocker.

Don't install updates
Don't install updates before performing any of the tests, as when you are testing pre-releases, available updates are not part of the proposed released package set.
Virtual machine testing
In most cases, testing in a virtual machine is OK. You can test UEFI (including SecureBoot) in VMs as well.

Results summary page[edit]

The Test Results:Fedora 25 Branched 20160927.n.0 Summary page contains the results from this page and all the other validation pages for the same compose listed together to provide an overview.

Add, Modify or Remove a Test Case[edit]

  1. Please request review for your changes by publishing your test case for review to the test mailing list and/or the appropriate working group mailing list (e.g. server, cloud, or desktop).
  2. Once reviewed, make your changes to any current documents that use the template (e.g. Test_Results:Current_Security Lab_Test).
  3. Lastly, update Template:Security Lab_test_matrix with the same changes.


See the table below for a sample format for test results. All test results are posted using the result template.

Test Result Explanation Code Entered
Untested - This test has not been run, and is available for anyone to contribute feedback. {{result|none}}
Pass pass robatino
Passed - The test has been run and the tester determine the test met the expected results {{result|pass|robatino}}
Inprogress inprogress adamwill
Inprogress - An inprogress result is often used for tests that take a long time to execute. Inprogress results should be temporary and change to pass, fail or warn. {{result|inprogress|adamwill}}
Fail fail jlaska [1] [2]
Failed - Indicates a failed test. A link to a bug must be provided. See Template:Result for details on providing bug information.
  1. RHBZ #XYZ
  2. RHBZ #ZXY
Warning warn rhe
Warning - This test completed and met the expected results of the test, but other issues were encountered during testing that warrant attention.
  1. Brief description about the warning status
{{result|warn|rhe}} <ref>Brief description about the warning status</ref>
Pass pass hongqing
Warning warn kparal
Multiple results - More people can easily provide results to a single test case. {{result|pass|hongqing}} {{result|warn|kparal}}
Fail fail pboy [1] [2]
Failed - Same issue with LVM again
  1. RHBZ #2246871
  2. RHBZ #'2244305
Pass pass previous <build> run
Result from previous test run - This test result is directly moved from the test run of previous <build>. {{result|pass|previous <build> run}}
Unsupported - An unsupported test or configuration. No testing is required.

Test Matrix[edit]

Milestone Test Case Security Lab
Beta QA:Testcase_Mediakit_ISO_Size
Beta QA:Testcase_Mediakit_ISO_Checksums
Beta QA:TestCases/Install_Source_Live_Image
Beta QA:Testcase_base_firstboot
Beta QA:Testcase_base_startup
Beta QA:Testcase_base_system_logging
Beta QA:Testcase_desktop_browser
Beta QA:Testcase_desktop_updates
Beta QA:Testcase_desktop_login
Beta QA:Testcase_desktop_panel_basic
Beta QA:Testcase_desktop_error_checks
Beta QA:Testcase_desktop_menus
Beta QA:Testcase_Nmap
Beta QA:Testcase_Wireshark
Beta QA:Testcase_Nikto
Beta QA:Testcase_OpenVAS
Beta QA:Testcase_HTTPing
Beta QA:Testcase_Rkhunter
Beta QA:Testcase_OpenSSH