From Fedora Project Wiki

(broken "Server validation testing" link should point to the generic Release validation testing page)
No edit summary
Line 107: Line 107:


<!--In real event, you need to change above category to:
<!--In real event, you need to change above category to:
[[Category: Fedora {19,20,21} {Alpha,Beta,Final} {TC,RC} Test Results|B]]
[[Category: Fedora {19,20,21} {Alpha,Beta,Final} {TC,RC} Test Results|S]]
-->
-->

Revision as of 15:08, 16 September 2014

This page is intended to record server validation testing test results for the Fedora (VERSION) (PRE-RELEASE) release.

How to test

  1. Download the ISO images for testing: please use one of the Network product installer images. Delta_ISOs for installer images are also available here.
  2. Perform one or more of the test cases and add your results to the table below.
  3. If a test fails, file a bug report, and propose the bug as a blocker for the appropriate release (see blocker 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 blocker. 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.
  4. 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.

Add or Remove a Test Case

  1. Please request review for your changes by publishing your test case for review to server@lists.fedoraproject.org.
  2. Lastly, update QA:Server validation results template with the same changes.

Key

See the table below for a sample format for test results. All test results are posted using the format specified Template:Result.


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

Release Level Test Case x86 ARM References
Alpha QA:Testcase_kickstart_firewall
none
none
Alpha QA:Testcase_realmd_join_kickstart
none
none
Alpha QA:Testcase_realmd_join_server
none
none
Alpha QA:Testcase_FreeIPA_realmd_join
none
none
Alpha QA:Testcase_Server_firewall_default
none
none
Alpha QA:Testcase_Server_cockpit_default
none
none