From Fedora Project Wiki
(obsolete) |
(automated category move, see https://lists.fedoraproject.org/pipermail/test/2014-October/123052.html) |
||
| Line 165: | Line 165: | ||
[[Category:Security_Lab_validation_testing]] | [[Category:Security_Lab_validation_testing]] | ||
[[Category: Fedora 16 Beta | [[Category: Fedora 16 Beta Test Results|S]] | ||
Latest revision as of 20:37, 1 October 2014
No longer current
This candidate is no longer the current milestone. For the latest results, see Test_Results:Current_Security_Lab_Test.
This candidate is no longer the current milestone. For the latest results, see Test_Results:Current_Security_Lab_Test.
This page records test results for the Fedora 16 Beta TC1 Security Lab Spin.
How to test[edit]
- Download the ISO images for testing: FIXME: point to the current Security Lab SPIN ISO.
- Install, if appropriate (some tests may be intended to test the un-installed live environment).
- Perform one or more of the test cases and add your results to the table below.
- If a test fails, file a bug report. If the bug is in the default desktop, propose the bug as a blocker for the appropriate release (see blocker bug process). If the bug is in any other desktop, propose it as a nice-to-have bug for the appropriate release (see nice-to-have bug process).
- Don't install updates before performing any of the tests, as the updates available come from updates-testing and are not part of the proposed released package set. For this reason, we recommend leaving the update installation test for last.
Virtual machine testing
In most cases, testing in a virtual machine is OK.
In most cases, testing in a virtual machine is OK.
Network Lab requirement
Some tests require a network lab with various services like SSH, HTTP, SMTP, DNS ..., and the firewall configured correctly to allow those services
Some tests require a network lab with various services like SSH, HTTP, SMTP, DNS ..., and the firewall configured correctly to allow those services
Add or Remove a Test Case[edit]
- Please request review for your changes by publishing your test case for review to test@lists.fedoraproject.org.
- Once reviewed, make your changes to any current documents that use this template (e.g. Test Results:Fedora 16 Beta TC1 Security Lab)
- Lastly, update Test Results:Fedora 16 Beta TC1 Security Lab with the same changes.
Key[edit]
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 |
|---|---|---|
| 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. |
