From Fedora Project Wiki

(KDE QA:Testcase_base_system_logging)
(manual category fixup (script borked at the end))
 
(15 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
{{admon/important|No longer current|This candidate is no longer the current milestone.  For the latest results, see [[Test_Results:Current_Base_Test]].}}
 +
 
This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha RC1''' release.
 
This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha RC1''' release.
  
Line 67: Line 69:
 
| Alpha
 
| Alpha
 
| [[QA:Testcase_base_initial_setup]]
 
| [[QA:Testcase_base_initial_setup]]
| {{result|none}}
+
| {{result|pass|roshi}}
| {{result|none}}
+
| {{result|fail|kparal}}<ref>no initial setup is run. should it, with server?</ref>
 
| {{result|pass|jreznik}}
 
| {{result|pass|jreznik}}
| {{result|none}}
+
| {{result|pass|pwhalen}}
 
| style="background:lightgrey;"|
 
| style="background:lightgrey;"|
 
| <references/>  
 
| <references/>  
Line 76: Line 78:
 
| Alpha
 
| Alpha
 
| [[QA:Testcase_base_startup]]
 
| [[QA:Testcase_base_startup]]
| {{result|none}}
+
| {{result|pass|roshi}}<ref>Did the GUI half of this test.</ref>
| {{result|none}}
+
| {{result|pass|roshi}}<ref>Did the txt half of this test.</ref>
| {{result|none}}
+
| {{result|pass|kparal}}
| {{result|none}}
+
| {{result|pass|pwhalen}}
 
| {{result|pass|hguemar}}
 
| {{result|pass|hguemar}}
 
| <references/>  
 
| <references/>  
Line 85: Line 87:
 
| Alpha
 
| Alpha
 
| [[QA:Testcase_base_system_logging]]
 
| [[QA:Testcase_base_system_logging]]
| {{result|none}}
+
| {{result|warn|roshi}}<ref>/var/log/secure doesn't exist on the workstation. Journal seems to be working as expected.</ref>
 
| {{result|pass|adamwill}}
 
| {{result|pass|adamwill}}
 
| {{result|pass|jreznik}}
 
| {{result|pass|jreznik}}
| {{result|none}}
+
| {{result|pass|pwhalen}}
 
| {{result|pass|hguemar}}
 
| {{result|pass|hguemar}}
 
| <references/>  
 
| <references/>  
Line 97: Line 99:
 
| {{result|warn|adamwill|892178}}
 
| {{result|warn|adamwill|892178}}
 
| {{result|none}}
 
| {{result|none}}
| {{result|none}}
+
| {{result|warn|pwhalen|892178}}
 
| {{result|pass|hguemar}}
 
| {{result|pass|hguemar}}
 
| <references/>  
 
| <references/>  
Line 106: Line 108:
 
| {{result|pass|adamwill}}
 
| {{result|pass|adamwill}}
 
| {{result|none}}
 
| {{result|none}}
| {{result|none}}
+
| {{result|pass|pwhalen}}
 
| {{result|pass|hguemar}}
 
| {{result|pass|hguemar}}
 
| <references/>  
 
| <references/>  
Line 115: Line 117:
 
| {{result|pass|adamwill}}
 
| {{result|pass|adamwill}}
 
| {{result|none}}
 
| {{result|none}}
| {{result|none}}
+
| {{result|pass|pwhalen}}
 
| {{result|pass|hguemar}}
 
| {{result|pass|hguemar}}
 
| <references/>  
 
| <references/>  
Line 122: Line 124:
  
 
[[Category:Base_validation_testing]]
 
[[Category:Base_validation_testing]]
[[Category: Fedora 21 Alpha RC Test Results|B]]
+
[[Category: Fedora 21 Alpha Test Results|B]]

Latest revision as of 21:40, 1 October 2014

Important.png
No longer current
This candidate is no longer the current milestone. For the latest results, see Test_Results:Current_Base_Test.

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

How to test[edit]

  1. Download the ISO images for testing: please use one of the release media for the Product being tested. Delta_ISOs for installer images are also available here. 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.
  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.
Note.png
Virtual machine testing
In most cases, testing in a virtual machine is OK.

Add or Remove a Test Case[edit]

  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. Test Results:Fedora 21 Alpha RC1 Base)
  3. Lastly, update QA:Base validation results template 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
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.


Test Matrix[edit]

Release Level Test Case Workstation Server KDE ARM Cloud References
Alpha QA:Testcase_base_initial_setup
Pass pass roshi
Fail fail kparal
[1]
Pass pass jreznik
Pass pass pwhalen
  1. no initial setup is run. should it, with server?
Alpha QA:Testcase_base_startup
Pass pass roshi
[1]
Pass pass roshi
[2]
Pass pass kparal
Pass pass pwhalen
Pass pass hguemar
  1. Did the GUI half of this test.
  2. Did the txt half of this test.
Alpha QA:Testcase_base_system_logging
Warning warn roshi
[1]
Pass pass adamwill
Pass pass jreznik
Pass pass pwhalen
Pass pass hguemar
  1. /var/log/secure doesn't exist on the workstation. Journal seems to be working as expected.
Final QA:Testcase_Services_start
none
Warning warn adamwill [1]
none
Warning warn pwhalen [1]
Pass pass hguemar
  1. 1.0 1.1 RHBZ #892178
Final QA:Testcase_base_selinux
none
Pass pass adamwill
none
Pass pass pwhalen
Pass pass hguemar
Final QA:Testcase_base_service_manipulation
none
Pass pass adamwill
none
Pass pass pwhalen
Pass pass hguemar