Search results

...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.

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).

...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 ===

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. [[

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

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

...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 ==

...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]]

...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

...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

...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]]

...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]]

...{{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

..._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.}}

...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]].

...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]].

General options: The page 'QA:Base validation results template' is not a test case

...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

| 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

...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]].

...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.

...for these releases for as long as there is community interest though we in general follow the 1-2-3 and out policy. This provides an effective supported lifet ...eneral user testing before being released. Only once we've received signed testing data verifying the update can it be released. Digital signatures at each st

...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]].

General Manual Test Use case： Manual testing Use Case:

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.

...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]].

...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]].

...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>

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.}}

=== 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,

This page is intended to record installation validation test results for Rawhide nightly builds in the month of July 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.}}

...tended to record installation [[QA:Release_validation_test_plan|validation testing]] test results for the ''' Fedora 21 PPC''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].

...month or something, then the question is how long something needs to be in testing. === General ===

...13 website banner designs, work on a LiveCD icon, and a call for help with testing the Fedora 13 Alpha backgrounds. This issue finishes off with a quiet week In this section, we cover announcements from the Fedora Project, including general announcements<ref>

...quest, desktop validation update, and an updated gnome-shell available for testing.In Translation news, a request for submission branches for Anaconda, notice In this section, we cover announcements from the Fedora Project, including general announcements<ref>

...ite Kola https://github.com/coreos/coreos-assembler/blob/main/docs/kola.md#testing-with-kola The release status can be tracked in each ticket. If each steps and validation were successful the release is considered GO.

...| 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 ...cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

This page is intended to record installation validation test results for Fedora 21 nightly builds in the month of August 2014. ...a TC, 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.}}

* F18 status, TC testing preparation * Multi-image validation

| 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

...cycle. The Artwork Team brings us news on the Fedora 14 artwork efforts, testing the new Fedora branding Fonts recently developed, and a mockup for the new In this section, we cover announcements from the Fedora Project, including general announcements<ref>

=== Quick debuginfo validation === checksums is sufficient for confidence in validation. The important change

* TC1 was available and testing in progress (but x86-64 images not yet done) ...ther a team of Red Hat interns in his local office to help with validation testing

This page is intended to record installation validation test results for Rawhide nightly builds in the month of May 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.}}

This page is intended to record installation validation test results for Rawhide nightly builds in the month of June 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.}}

* Live CD testing was introduced in [[QA/TestResults/Fedora9LiveCD/FinalRelease]] (and droppe ...and [https://www.happyassassin.net/2014/12/24/fedora-22-and-later-nightly-testing/ automatic generation of nightly result pages] were introduced in [[:Catego

...de-redhat, and the availability of KDE SC 4.4rc2 live images available for testing. That rounds out FWN 212 -- read on! In this section, we cover announcements from the Fedora Project, including general announcements<ref>

...on with the Fedora QA Team for help with the Fedora Localization Project's testing events, and an announcement of new team members for French, Arabic and Russ In this section, we cover announcements from the Fedora Project, including general announcements<ref>

...er thing that seemed a good idea to me would be to go through the alpha rc validation results and check that bugs are appropriately flagged as blockers for futur ...g forward with the features planned for 0.7.0 but other than that, will be testing F16

| 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