From Fedora Project Wiki
< User:Roshi | QA/Cloud Docs
(Created page with "This page records base cloud system validation testing test results for the Fedora '''21 Alpha TC1''' release. == How to test == <!--Plea...") |
(drafts out of categories now!) |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 5: | Line 5: | ||
<!--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.--> | <!--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.--> | ||
# Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21-Alpha-TC1/ release media for the Product being tested | # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21-Alpha-TC1/ release media for the Product being tested]. Some tests may specify use of a specific cloud provider; please follow these specifications. | ||
# Perform one or more of the [[:Category: | # Perform one or more of the [[:Category:Cloud_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], 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. | ||
| Line 15: | Line 15: | ||
# Please request review for your changes by publishing your test case for review to [mailto:test@lists.fedoraproject.org test@lists.fedoraproject.org]. {{#ifeq: {{FULLPAGENAME}} | QA:Desktop validation results template || | # Please request review for your changes by publishing your test case for review to [mailto:test@lists.fedoraproject.org test@lists.fedoraproject.org]. {{#ifeq: {{FULLPAGENAME}} | QA:Desktop validation results template || | ||
# Once reviewed, make your changes to any current documents that use this template (e.g. {{FULLPAGENAME}}) }} | # Once reviewed, make your changes to any current documents that use this template (e.g. {{FULLPAGENAME}}) }} | ||
# Lastly, update [[QA: | # Lastly, update [[QA:Cloud base validation results template]] with the same changes. | ||
== Key == | == Key == | ||
| Line 66: | Line 66: | ||
|- | |- | ||
| Alpha | | Alpha | ||
| [[QA: | | [[QA:Testcase_Cloud_ssh]] | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|none}} | | {{result|none}} | ||
| Line 116: | Line 109: | ||
|- | |- | ||
| Alpha | | Alpha | ||
| [[QA: | | [[QA:Testcase_Cloud_ssh]] | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|none}} | | {{result|none}} | ||
| Line 158: | Line 144: | ||
|- | |- | ||
|} | |} | ||
Latest revision as of 21:29, 30 September 2014
This page records base cloud system validation testing test results for the Fedora 21 Alpha TC1 release.
How to test
- 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.
- 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.
Local Testing
In most cases, testing in locally with qemu is acceptable.
In most cases, testing in locally with qemu is acceptable.
Add or Remove a Test Case
- 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. User:Roshi/QA/Cloud Docs/Alpha Release Validation)
- 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 |
|---|---|---|
| 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. |
x86_64 Test Matrix
| Release Level | Test Case | Local | EC2 | OpenShift | References |
|---|---|---|---|---|---|
| Alpha | QA:Testcase_Cloud_ssh | ||||
| Alpha | QA:Testcase_base_system_logging | ||||
| Final | QA:Testcase_Services_start | ||||
| Final | QA:Testcase_base_selinux | ||||
| Final | QA:Testcase_base_service_manipulation |
i386 Test Matrix
| Release Level | Test Case | Local | EC2 | OpenShift | References |
|---|---|---|---|---|---|
| Alpha | QA:Testcase_Cloud_ssh | ||||
| Alpha | QA:Testcase_base_system_logging | ||||
| Final | QA:Testcase_Services_start | ||||
| Final | QA:Testcase_base_selinux | ||||
| Final | QA:Testcase_base_service_manipulation |