From Fedora Project Wiki
Important.png
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 General validation testing test results for the Fedora-IoT 33 20201020.0 nightly compose.

Which tests to run

Note.png
Test coverage page
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

1. Download one or more media for testing:

Image aarch64 armhfp x86_64
IoT raw-xz Download Download Download
IoT dvd Download Download Download
IoT dvd-ostree Download Download 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 --dist Fedora-IoT 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.


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.

Important.png
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.
Note.png
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

The Test Results:Fedora-IoT 33 RC 20201020.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

  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. iot).
  2. Once reviewed, make your changes to any current documents that use the template (e.g. Test_Results:Current_IoT_General_Test).
  3. Lastly, update Template:General_IoT_test_matrix with the same changes.

Key

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
none
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
{{result|fail|jlaska|XYZ|ZXY}}
Warning warn rhe
[1]
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}}
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

ISO Install

Milestone Test Case x86_64 aarch64
Basic QA:Testcase_Boot_default_install
Pass pass OpenQA
Pass pass pwhalen
Basic QA:Testcase_Anaconda_User_Interface_Graphical
Pass pass OpenQA
Pass pass pwhalen
Basic QA:Testcase_Anaconda_user_creation
Pass pass OpenQA
Pass pass pwhalen
Basic QA:Testcase_partitioning_guided_empty
Pass pass OpenQA
Pass pass pwhalen
Optional QA:Testcase_USB_dd
none
none


Network boot

Milestone Test Case x86_64 aarch64
Basic QA:Testcase_Boot_Methods_Pxeboot
Pass pass pwhalen
Pass pass pwhalen
Optional QA:Testcase_Zezere_HTTP_Boot
none


Storage devices

Milestone Test Case x86_64 aarch64
Basic QA:Testcase_install_to_SATA
Pass pass pwhalen
Pass pass pwhalen
Beta QA:Testcase_install_to_VirtIO
Pass pass pwhalen
Pass pass pwhalen


Virtualization

Milestone Test Case x86_64 aarch64
Basic QA:Testcase_Install_to_Previous_KVM
Pass pass pwhalen
Pass pass pwhalen
Beta QA:Testcase_Install_to_Current_KVM
Pass pass pwhalen
Pass pass pwhalen


Disk Image Deployment

Milestone Test Case Raspberry Pi 3 Pine64 Rock960 Consumer Edition DragonBoard 410c x86_64 System
Basic QA:Testcase_arm_image_deployment
Pass pass pwhalen
none
none
none
none


Base

Milestone Test Case x86_64 aarch64
Basic QA:Testcase_Zezere_Ignition
Pass pass OpenQA
Pass pass pwhalen
Basic QA:Testcase_RpmOstree_Upgrade
Pass pass pwhalen
Pass pass pwhalen
Basic QA:Testcase_RpmOstree_Package_Layering
Pass pass pwhalen
Pass pass pwhalen
Basic QA:Testcase_RpmOstree_Rebase
Pass pass OpenQA
Pass pass pwhalen
Basic QA:Testcase_Podman
Pass pass OpenQA
Pass pass OpenQA
Basic QA:Testcase_base_startup
Pass pass OpenQA
Pass pass OpenQA
Basic QA:Testcase_base_reboot_unmount
Pass pass OpenQA
Pass pass OpenQA
Basic QA:Testcase_base_system_logging
Pass pass OpenQA
Pass pass OpenQA
Final QA:Testcase_base_edition_self_identification
Pass pass OpenQA
Pass pass OpenQA
Final QA:Testcase_base_services_start
Pass pass OpenQA
Pass pass OpenQA
Final QA:Testcase_base_selinux
Pass pass OpenQA
Pass pass OpenQA
Final QA:Testcase_base_service_manipulation
Pass pass OpenQA
Pass pass OpenQA

Hardware Tests

Milestone Test Case Raspberry Pi 3 Pine64 Rock960 Consumer Edition DragonBoard 410c Compulab Fitlet2
Basic Serial Console
none
none
none
none
none
Basic Display
Pass pass pwhalen
none
none
none
Pass pass pwhalen
Basic Wired Network
Pass pass pwhalen
none
none
none
Pass pass pwhalen
Basic Wi-Fi
Pass pass pwhalen
none
none
none
Pass pass pwhalen
Optional Bluetooth
none
none
none
none


Final

Milestone Test Case x86_64 aarch64
Final QA:Testcase_Greenboot
Pass pass pwhalen
Pass pass pwhalen
Final QA:Testcase_Clevis
Pass pass pwhalen