From Fedora Project Wiki
(First version)
 
No edit summary
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
This page records test results for the Fedora '''16 (PRE-RELEASE)''' [https://fedoraproject.org/wiki/Security_Lab Security Lab Spin].
== How to test ==
<!--If there are live images built for the pre-release being tested, change the link in the first step to point to the appropriate directory on serverbeach1-->
# 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 [[:Category:Desktop_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]. If the bug is in the default desktop, propose the bug as a blocker for the appropriate release (see [[QA:SOP_blocker_bug_process|blocker bug process]]). If the bug is in any other desktop, propose it as a nice-to-have bug for the appropriate release (see [[QA:SOP_nth_bug_process|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.
{{admon/note|Virtual machine testing|In most cases, testing in a virtual machine is OK.}}
{{admon/important|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}}
== Add 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].
# Once reviewed, make your changes to any current documents that use this template (e.g. {{FULLPAGENAME}})
# Lastly, update [[{{FULLPAGENAME}}]] 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]].
{| class="wikitable sortable" border="0"
! Test Result !! Explanation !! Code Entered
|-
| {{result|none}}
| ''Untested'' - This test has not been run, and is available for anyone to contribute feedback.
| <code><nowiki>{{result|none}}</nowiki></code>
|-
| {{result|pass|robatino}}
| ''Passed'' - The test has been run and the tester determine the test met the ''expected results''
| <code><nowiki>{{result|pass|robatino}}</nowiki></code>
|-
| {{result|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.
| <code><nowiki>{{result|inprogress|adamwill}}</nowiki></code>
|-
| {{result|fail|jlaska|XYZ|ZXY}}
| ''Failed'' - Indicates a failed test.  A link to a bug must be provided.  See [[Template:Result]] for details on providing bug information. <references/>
| <code><nowiki>{{result|fail|jlaska|XYZ|ZXY}}</nowiki></code>
|-
| {{result|warn|rhe}} <ref>Brief description about the warning status</ref>
| ''Warning'' - This test completed and met the ''expected results'' of the test, but other issues were encountered during testing that warrant attention.<references/>
| <code><nowiki>{{result|warn|rhe}} <ref>Brief description about the warning status</ref></nowiki></code>
|-
| {{result|pass|hongqing}} {{result|warn|kparal}}
| ''Multiple results'' - More people can easily provide results to a single test case.
| <code><nowiki>{{result|pass|hongqing}} {{result|warn|kparal}}</nowiki></code>
|-
| {{result|pass|previous <build> run}}
| ''Result from previous test run'' - This test result is directly moved from the test run of previous ''<build>''.<references/>
| <code><nowiki>{{result|pass|previous <build> run}}</nowiki></code>
|-
| style="background:lightgrey;"| {{testresult/none}} {{result|none}}
| ''Unsupported'' - An unsupported test or configuration.  No testing is required.
|
|-
|}
== '''Test Matrix''' ==
{| class="wikitable sortable" border="1"
{| class="wikitable sortable" border="1"
! Test Case  !! [[Security_Lab]] !! References
! Test Case  !! [[Security_Lab]] !! References
Line 11: Line 74:
|-
|-
| [[QA:TestCases/Install_Source_Live_Image]]
| [[QA:TestCases/Install_Source_Live_Image]]
| {{result|unknown|SampleUser}}
| <references/>
|-
| [[QA:Testcase_base_firstboot]]
| {{result|unknown|SampleUser}}
| <references/>
|-
| [[QA:Testcase_base_startup]]
| {{result|unknown|SampleUser}}
| {{result|unknown|SampleUser}}
| <references/>
| <references/>
Line 66: Line 137:
| <references/>
| <references/>
|-
|-
|-
| [[QA:Testcase_OpenSSH]]
| {{result|unknown|SampleUser}}
| <references/>
|}
|}

Latest revision as of 13:51, 28 June 2011

This page records test results for the Fedora 16 (PRE-RELEASE) Security Lab Spin.

How to test

  1. Download the ISO images for testing: FIXME: point to the current Security Lab SPIN ISO.
  2. Install, if appropriate (some tests may be intended to test the un-installed live environment).
  3. Perform one or more of the test cases and add your results to the table below.
  4. 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).
  5. 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.
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

Add or Remove a Test Case

  1. Please request review for your changes by publishing your test case for review to test@lists.fedoraproject.org.
  2. Once reviewed, make your changes to any current documents that use this template (e.g. User:Athmane/Draft Security Lab validation matrix)
  3. Lastly, update User:Athmane/Draft Security Lab validation matrix 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}}
none
Unsupported - An unsupported test or configuration. No testing is required.

Test Matrix

Test Case Security_Lab References
QA:Testcase_Mediakit_ISO_Size
Unknown unknown SampleUser
QA:Testcase_Mediakit_ISO_Checksums
Unknown unknown SampleUser
QA:TestCases/Install_Source_Live_Image
Unknown unknown SampleUser
QA:Testcase_base_firstboot
Unknown unknown SampleUser
QA:Testcase_base_startup
Unknown unknown SampleUser
QA:Testcase_base_system_logging
Unknown unknown SampleUser
QA:Testcase_desktop_browser
Unknown unknown SampleUser
QA:Testcase_desktop_updates
Unknown unknown SampleUser
QA:Testcase_desktop_login
Unknown unknown SampleUser
QA:Testcase_desktop_panel_basic
Unknown unknown SampleUser
QA:Testcase_desktop_error_checks
Unknown unknown SampleUser
QA:Testcase_desktop_menus
Unknown unknown SampleUser
QA:Testcase_Nmap
Unknown unknown SampleUser
QA:Testcase_Wireshark
Unknown unknown SampleUser
QA:Testcase_Nikto
Unknown unknown SampleUser
QA:Testcase_OpenVAS
Unknown unknown SampleUser
QA:Testcase_HTTPing
Unknown unknown SampleUser
QA:Testcase_Rkhunter
Unknown unknown SampleUser
QA:Testcase_OpenSSH
Unknown unknown SampleUser
Retrieved from "https://fedoraproject.org/w/index.php?title=User:Athmane/Draft_Security_Lab_validation_matrix&oldid=243243"