From Fedora Project Wiki
No edit summary
(test)
Line 1: Line 1:
[https://bugzilla.redhat.com/enter_bug.cgi file a bug report]
<noinclude>{{tempdoc}}</noinclude>
 
This page records {{{testtype|'''$testtype'''}}} [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora {{{release|'''$release'''}}} {{{milestone|'''$milestone'''}}} {{{compose|'''$compose'''}}} release.
 
== How to test ==
 
<!--Please change the link in the first step to point to the appropriate subdirectory of http://dl.fedoraproject.org/pub/alt/stage/ for the candidate build under test.-->
 
# [https://dl.fedoraproject.org/pub/alt/stage/{{{release|}}}_{{{milestone|}}}_{{{compose|}}} Download the media for testing].
# Perform one or more of the [[:Category:Base_Acceptance_Test_Cases|test cases]] and add your results to the table below.
# If a test fails, [https://bugzilla.redhat.com/enter_bug.cgi file a bug report]. You may [https://qa.fedoraproject.org/blockerbugs/propose_bug propose the bug as a release blocker or freeze exception bug] for the appropriate release - see [[QA:SOP_blocker_bug_process|blocker bug process]] and [[QA:SOP_freeze_exception_bug_process|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 [http://dl.fedoraproject.org/pub/alt/stage/deltaisos/{{{release|}}}_{{{milestone|}}}_{{{compose|}}}_Server 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.
 
{{admon/important|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.}}
 
{{admon/note|Virtual machine testing|In most cases, testing in a virtual machine is OK.}}
 
== Add, Modify or Remove a Test Case ==
# Please request review for your changes by publishing your test case for review to ).
# Once reviewed, make your changes to any current documents that use the template (e.g. [[Test_Results:Current_{{{testtype|$testtype}}}_Test]]).
# Lastly, update [[Template:{{{testtype|$testtype}}}_test_matrix]] with the same changes.

Revision as of 21:00, 23 September 2014

Template documentation [edit]

This documentation is transcluded from Template:Adamwill/Test page/doc. It will not be transcluded on pages that use this template.
Template:Adamwill/Test page/doc

This page records $testtype validation testing test results for the Fedora $release $milestone $compose release.

How to test

  1. Download the media for testing.
  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. 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.

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.

Add, Modify or Remove a Test Case

  1. Please request review for your changes by publishing your test case for review to ).
  2. Once reviewed, make your changes to any current documents that use the template (e.g. Test_Results:Current_$testtype_Test).
  3. Lastly, update Template:$testtype_test_matrix with the same changes.