This page records base validation testing test results for Rawhide nightly builds in the month of April 2014.
How to test
- Download the required Rawhide nightly live image, x86_64 or i386 network install image, or ARM disk image. If you use the network install image, enter the date on which you downloaded it as the 'build date' in your results (see #Key). Some tests may specify use of either a traditional installer image (the DVD image, or a net install image) or a live image; please follow these specifications. Note that if generation of the
boot.isoimages fails for a given day, the file will not be present on the mirrors (the last successful compose is not retained). In this case, you just have to wait for a successful compose, or use one of the other images/methods described on this page.
- Perform one or more of the test cases and add your results to the table below.
- 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.
- 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.
Add or Remove a Test Case
- Please request review for your changes by publishing your test case for review to email@example.com.
- Once reviewed, make your changes to any current documents that use this template (e.g. Test Results:Fedora 21 Rawhide 2014 04 Base)
- Lastly, update QA:Base validation results template with the same changes.
See the table below for a sample format for test results. All test results are posted using the format specified Template:Result.
|Test Results Format|
|Test Result||Explanation||Code Entered|
|Untested - This test has not been run, and is available for anyone to contribute feedback.|
|Passed - The test has been run and the tester determine the test met the expected results. The date of the build tested (not the date the test was run) should be included.|
|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.|
|Failed - Indicates a failed test. A link to a bug must be provided. See Template:Result for details on providing bug information. The date of the build tested (not the date the test was run) should be included.|
| 20140415||Warning - This test completed and met the expected results of the test, but other issues were encountered during testing that warrant attention. The date of the build tested (not the date the test was run) should be included.
|Multiple results - More people can easily provide results to a single test case.|
|Unsupported - An unsupported test or configuration. No testing is required.|
|Release Level||Test Case||x86(_64)||ARM||Cloud||References|