From Fedora Project Wiki

  • ...pages as appropriate. If all you need to do is add, remove or edit an IoT validation test case, though, don't worry about that stuff, and put it in here.
    447 bytes (76 words) - 23:29, 13 May 2020
  • In general terms, when you build an RPM, there are two things you have to test: ...above did not have to be repeated, and more effort could be focused on the testing to meet condition (2).
    2 KB (324 words) - 18:03, 4 March 2009
  • ...and pre-release is made, to ensure they reach [[Fedora_Release_Criteria]]. Testing covers the [[QA:Installation_validation_testing|installation process]] and === Differs from release validation events ===
    6 KB (948 words) - 22:27, 28 July 2011
  • 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
  • This page is intended to record [[QA/Join#Release_validation|Release Validation]] test results for the '''{{FedoraVersion|long|next}}''' release. * Most testing can occur using rawhide -- [[Releases/Rawhide#Direct_Rawhide_install|Consul
    3 KB (456 words) - 16:32, 9 February 2010
  • This document describes how this testing is carried out. You can contribute by downloading the nightly composes and Testing will involve executing test cases to verify installation and basic function
    12 KB (1,795 words) - 10:18, 6 August 2020
  • ...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
  • ...Releases/|stable release]], new packages from [[QA:Updates_Testing|updates-testing]], or the bleeding edge [[Releases/Rawhide|Rawhide]], QA has a way for you ** [[#release-validation|Release Validation Testing]]
    9 KB (1,397 words) - 06:07, 20 September 2016
  • ...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
  • ...{{testtype|'''$testtype'''}}} [[QA:Release_validation_test_plan|validation testing]] test results for the {{{dist|Fedora}}} {{{release|'''$release'''}}} {{#if 1. Download one or more media for testing{{#ifeq:{{{testtype|}}}|Cloud|, or for EC2 tests, locate and use an appropri
    7 KB (1,085 words) - 07:11, 1 November 2023
  • ..._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''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].
    21 KB (2,748 words) - 04:26, 11 September 2014
  • ...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
  • General options: The page 'QA:Base validation results template' is not a test case
    6 KB (816 words) - 10:23, 23 August 2011
  • ...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
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)