From Fedora Project Wiki
No edit summary
(drafts out of categories now!)
 
(5 intermediate revisions by one other user not shown)
Line 9: Line 9:
# If a test fails, [https://bugzilla.redhat.com/enter_bug.cgi file a bug report], and propose the bug as a blocker for the appropriate release (see [[QA:SOP_blocker_bug_process|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.
# If a test fails, [https://bugzilla.redhat.com/enter_bug.cgi file a bug report], and propose the bug as a blocker for the appropriate release (see [[QA:SOP_blocker_bug_process|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.
# 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|Local Testing|In most cases, testing in locally with qemu is acceptable.}}


== Add or Remove a Test Case ==
== Add or Remove a Test Case ==
Line 80: Line 78:
|-
|-
| Alpha
| Alpha
| [[QA:Testcase_Cloud_package_installation]]
| [[QA:Testcase_CLI_package_installation]]
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
Line 101: Line 99:
|-
|-
| Beta
| Beta
| [[QA:Testcase_Cloud_package_upgrade]]
| [[QA:Testcase_CLI_package_upgrade]]
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
Line 122: Line 120:
|-
|-
| Beta
| Beta
| [[QA:Testcase_Cloud_selinux]]
| [[QA:Testcase_base_selinux]]
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
Line 171: Line 169:
|-
|-
| Alpha
| Alpha
| [[QA:Testcase_Cloud_package_installation]]
| [[QA:Testcase_CLI_package_installation]]
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
Line 192: Line 190:
|-
|-
| Beta
| Beta
| [[QA:Testcase_Cloud_package_upgrade]]
| [[QA:Testcase_CLI_package_upgrade]]
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
Line 213: Line 211:
|-
|-
| Beta
| Beta
| [[QA:Testcase_Cloud_selinux]]
| [[QA:Testcase_base_selinux]]
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
Line 241: Line 239:
|-
|-
|}
|}
[[Category:Base_validation_testing]]
[[Category: Fedora 21 Alpha TC Test Results|B]]

Latest revision as of 21:30, 30 September 2014

This page records base cloud system validation testing test results for the Fedora 21 Alpha TC1 release.

How to test

  1. Download the ISO images for testing: please use one of the release media for the Product being tested. Some tests may specify use of a specific cloud provider; please follow these specifications.
  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, 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.
  4. 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

  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:Roshi/QA/Cloud Docs/Cloud Release Validation)
  3. Lastly, update QA:Cloud base validation results template 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}}
Unsupported - An unsupported test or configuration. No testing is required.


x86_64 Test Matrix

Release Level Test Case Local EC2 OpenShift References
Alpha QA:Testcase_Cloud_ssh
none
none
none
Alpha QA:Testcase_base_system_logging
none
none
none
Alpha QA:Testcase_CLI_package_installation
none
none
none
Alpha QA:Testcase_Cloud_serial_console
none
none
none
Alpha QA:Testcase_Services_start
none
none
none
Beta QA:Testcase_CLI_package_upgrade
none
none
none
Beta QA:Testcase_Cloud_firewall_disabled
none
none
none
Beta QA:Testcase_Cloud_root_disabled
none
none
none
Beta QA:Testcase_base_selinux
none
none
none
Final QA:Testcase_Cloud_sudo
none
none
none
Final QA:Testcase_Cloud_external_configuration_tools
none
none
none
Final QA:Testcase_base_service_manipulation
none
none
none

i386 Test Matrix

Release Level Test Case Local EC2 OpenShift References
Alpha QA:Testcase_Cloud_ssh
none
none
none
Alpha QA:Testcase_base_system_logging
none
none
none
Alpha QA:Testcase_CLI_package_installation
none
none
none
Alpha QA:Testcase_Cloud_serial_console
none
none
none
Alpha QA:Testcase_Services_start
none
none
none
Beta QA:Testcase_CLI_package_upgrade
none
none
none
Beta QA:Testcase_Cloud_firewall_disabled
none
none
none
Beta QA:Testcase_Cloud_root_disabled
none
none
none
Beta QA:Testcase_base_selinux
none
none
none
Final QA:Testcase_Cloud_sudo
none
none
none
Final QA:Testcase_Cloud_external_configuration_tools
none
none
none
Final QA:Testcase_base_service_manipulation
none
none
none