(update link to the template to edit for the test matrix) |
(fix up the test case revision instructions) |
||
Line 21: | Line 21: | ||
{{admon/note|Virtual machine testing|In most cases, testing in a virtual machine is OK.}} | {{admon/note|Virtual machine testing|In most cases, testing in a virtual machine is OK.}} | ||
== Add or Remove a Test Case == | == Add, Modify or Remove a Test Case == | ||
# Please request review for your changes by publishing your test case for review to [mailto:test@lists.fedoraproject.org test@lists.fedoraproject.org]. | # Please request review for your changes by publishing your test case for review to [mailto:test@lists.fedoraproject.org test@lists.fedoraproject.org] and/or the appropriate working group mailing list (e.g. mailto:server@lists.fedoraproject.org server@], mailto:cloud@lists.fedoraproject.org cloud@], or [mailto:desktop@lists.fedoraproject.org desktop@]. | ||
# Once reviewed, make your changes to any current documents that use | # Once reviewed, make your changes to any current documents that use the template (e.g. [[{{Current_{{{testtype|$testtype}}}_Test]]). | ||
# Lastly, update [[Template:{{{testtype|$testtype}}}_test_matrix]] with the same changes. | # Lastly, update [[Template:{{{testtype|$testtype}}}_test_matrix]] with the same changes. | ||
Revision as of 04:03, 23 September 2014
Template documentation [edit]
- This documentation is transcluded from Template:Release validation instructions/doc. It will not be transcluded on pages that use this template.
This page records $testtype validation testing test results for the Fedora $release $milestone $compose release.
How to test
- Download the media for testing.
- Perform one or more of the test cases and add your results to the table below.
- 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.
Delta_ISOs for Server offline installer images are available here. If you have the Server offline install image for the previous TC/RC (or in the case of Alpha TC1, the previous stable release), you can generate the current install image with greatly reduced download size.
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.
Add, Modify or Remove a Test Case
- Please request review for your changes by publishing your test case for review to test@lists.fedoraproject.org and/or the appropriate working group mailing list (e.g. mailto:server@lists.fedoraproject.org server@], mailto:cloud@lists.fedoraproject.org cloud@], or desktop@.
- Once reviewed, make your changes to any current documents that use the template (e.g. [[{{Current_$testtype_Test]]).
- Lastly, update Template:$testtype_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 |
---|---|---|
Untested - This test has not been run, and is available for anyone to contribute feedback. | {{result|none}}
| |
robatino
|
Passed - The test has been run and the tester determine the test met the expected results | {{result|pass|robatino}}
|
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}}
| |
Failed - Indicates a failed test. A link to a bug must be provided. See Template:Result for details on providing bug information. | {{result|fail|jlaska|XYZ|ZXY}}
| |
[1] | Warning - This test completed and met the expected results of the test, but other issues were encountered during testing that warrant attention.
|
{{result|warn|rhe}} <ref>Brief description about the warning status</ref>
|
Multiple results - More people can easily provide results to a single test case. | {{result|pass|hongqing}} {{result|warn|kparal}}
| |
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. |