From Fedora Project Wiki

  • This page records [[QA:Desktop_validation_testing|desktop validation testing]] test results for the Fedora '''16 Alpha RC3''' release. ...alt/stage/16-Alpha.RC3/Live/ live image] for the desktop you wish to test. Testing for all four major desktop environments is required for each test point. [[
    7 KB (1,055 words) - 20:40, 1 October 2014
  • ...Release_validation_test_plan|release validation testing process]], and for testing updates. On this page you can find more information about openQA, how Fedor == General information ==
    11 KB (1,686 words) - 06:04, 25 July 2023
  • ...e to the Fedora QA project page. Fedora QA is the project which covers all testing of the software that makes up Fedora. It's our goal to continually improve ...[[Releases/Branched|Branched]] pre-releases, [[QA:Updates_Testing|updates-testing]], or as it appears in a supported public release
    5 KB (776 words) - 12:42, 18 January 2024
  • ...e to the Fedora QA project page. Fedora QA is the project which covers all testing of the software that makes up Fedora. It's our goal to continually improve ...[[Releases/Branched|Branched]] pre-releases, [[QA:Updates_Testing|updates-testing]], or as it appears in a supported public release
    5 KB (736 words) - 13:08, 7 April 2021
  • ...Releases|stable release]], a new package from [[QA:Updates_Testing|updates-testing]], a [[Releases/Branched|Branched]] [https://fedoraproject.org/get-prerelea ** [[#release-validation|Release Validation Testing]]
    10 KB (1,635 words) - 14:16, 14 March 2024
  • ...Releases|stable release]], a new package from [[QA:Updates_Testing|updates-testing]], a [[Releases/Branched|Branched]] [https://fedoraproject.org/get-prerelea ** [[#release-validation|Release Validation Testing]]
    10 KB (1,573 words) - 22:55, 31 August 2022
  • ..._plan]]. This page provides guidance on arranging and announcing a release validation test event. For any concerns, please contact the [[QA]] group. ...s process. This SOP can still be followed in any unusual case where manual validation event creation is still required.}}
    12 KB (1,870 words) - 13:12, 15 December 2023
  • ...tended to record installation [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 Alpha TC1''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].
    22 KB (2,849 words) - 14:52, 11 September 2014
  • ...t of characters will be available for testing, workarounds, bug fixes, and general discussion ... This testing effort will focus on improvements in the way in which anaconda interacts wi
    8 KB (1,087 words) - 19:46, 26 June 2015
  • | image = [[File:Echo-testing-48px.png|link=QA/Test Days]] ...| If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, fi
    5 KB (756 words) - 15:40, 19 May 2020
  • ...tended to record installation [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 Alpha TC7''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].
    20 KB (2,648 words) - 18:50, 14 October 2014
  • ...calable compose''' to enable CI/CD operations; we need to '''automate more testing and quality measures'''; and we need to '''update our delivery tools and pr ...osal. It doesn’t technically block them, although failure to coordinate in general surely would.
    10 KB (1,575 words) - 17:41, 6 January 2019
  • ...tended to record installation [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 Alpha TC5''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].
    20 KB (2,686 words) - 18:49, 14 October 2014
  • General Manual Test Use case: Manual testing Use Case:
    3 KB (446 words) - 10:06, 16 December 2010
  • The testing build of unbound server with the mixed-mode module can be found in the [htt ...but they are hijacking a non-existing TLD and this would cause the DNSSEC validation to fail.
    14 KB (2,012 words) - 09:34, 11 February 2016
  • ...tended to record installation [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 Alpha TC6''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].
    20 KB (2,712 words) - 18:50, 14 October 2014
  • ...tended to record installation [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 Alpha RC1''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].
    22 KB (2,858 words) - 18:51, 14 October 2014
  • ...ance news, draft standard operating procedures for QA meetings, validation testing updates and more. FWN 282 finishes off this week with a few security advis In this section, we cover announcements from the Fedora Project, including general announcements<ref>
    25 KB (3,616 words) - 16:20, 22 July 2011
  • This page is intended to record installation validation test results for Rawhide nightly builds in the month of April 2014. ...tone, however no-one should feel obliged in any way to participate in this testing, and certainly not to work excessively long, late or hard on it.}}
    21 KB (2,623 words) - 22:35, 19 December 2014
  • === New proposed release validation matrices === ...edoraproject.org/wiki/User:Adamwill/Draft_base_validation_matrix</ref> for validation tests which do not fit under the existing 'install' or 'desktop' matrices,
    19 KB (2,723 words) - 15:20, 12 July 2011
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)