Search results

Test cases that validate the Server-specific [[Fedora Release Criteria]]. [[Category:Server validation testing]]

...is intended to record server [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC1''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/F21a-TC1

...is intended to record server [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC5''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21-Alpha

...is intended to record server [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC7''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21_Alpha

...is intended to record server [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 PPC''' release. # Download the ISO images for testing: please use one of the [https://ppc.koji.fedoraproject.org/stage/ Network p

...is intended to record server [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha RC1''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21_Alpha

...is intended to record server [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC6''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21_Alpha

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''18 Final RC4''' release. # Download the ISO images for testing: please use either a [https://download.fedoraproject.org/pub/fedora/linux/r

This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 PPC''' release. ( Workstation, Server, KDE, ARM, Cloud, References)

This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC1''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/F21a-TC1

This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha RC1''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21_Alpha

This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC7''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21_Alpha

This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC6''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21_Alpha

This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC5''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21-Alpha

This page records [[QA:Desktop_validation_testing|desktop validation testing]] test results for the Fedora '''14 Alpha Test Compose 2''' release. ...be kept on the server during the TC2 test period. Please use these images. Testing for all four major desktop environments is required for each test point. De

This page records [[QA:Desktop_validation_testing|desktop validation testing]] test results for the Fedora '''17 Beta RC4''' release. .../releases/test/17-Beta/Live/ live image] for the desktop you wish to test. Testing for all four major desktop environments is required for each test point. [[

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= F21 RC1 - AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

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

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

...Release_validation_test_plan|release validation testing process]], and for testing updates. On this page you can find more information about openQA, how Fedor openQA is an automated test system designed around operating system-level testing. Its key feature is that it interacts with the system under test much like

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

...k|This page describes '''experimental''' and unofficial module for unbound server!}} The testing build of unbound server with the mixed-mode module can be found in the [http://copr-fe.cloud.fedora

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

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

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

...included on this page because all the same tests are present on the Cloud validation page.}} ! Milestone !! Test Case !! Workstation !! Server !! KDE

= Framework for Server Role Deployment = A new D-Bus service, and associated command-line tools, to deploy and manage Server Roles.

...erly. The root zone provides a global trust anchor that in turn allows for validation of DNS records in signed zones. Other trust anchors can be configured to ex ...e local validating resolver which reports name resolution failure whenever validation of a DNS record fails. On the other hand, applications that know about DNSS

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

records usually from a DNSSEC-compliant recursive DNS server. The validator recursive DNS server is needed.

...S. Built on standard web protocols, WebHDFS decouples the HDFS client and server and is language- and operating system-agnostic. WebHDFS makes it easy to in ...proach. This will be done by designing or adopting an API, implementing a server, and validating correctness and evaluating performance under various use ca

...S. Built on standard web protocols, WebHDFS decouples the HDFS client and server and is language- and operating system-agnostic. WebHDFS makes it easy to in ...proach. This will be done by designing or adopting an API, implementing a server, and validating correctness and evaluating performance under various use ca

...change is to promote Fedora CoreOS to Edition status alongside Cloud, IoT, Server and Workstation. ...change is to promote Fedora CoreOS to Edition status alongside Cloud, IoT, Server and Workstation.

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

...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 We need faster composes, to enable more continuous testing/integration/delivery. In a continuous process, changes are checked not just

...a graphical mechanism for deploying a FreeIPA Domain Controller on Fedora Server through the Cockpit administrative console. * Email: server@lists.fedoraproject.org

server administration team, the SAN administration team, and others (network, etc.) not relevant to this discussion. Within the server

...e AD flag to calling applications. This tricks applications into believing validation results of random servers received through DHCP and other means, which are * Trusted and untrusted for DNSSEC validation servers cannot be mixed.

...ain) version 9.10 is the latest stable major update of the widely used DNS server. Besides new features, some settings defaults have changed since the previo ...y if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)

...epo heirarchies do something like that already kde-unstable depends on kde-testing depends on kde-stable ...r packages against this. Bob shares his gtk2newness koper with others for validation of the new GTK2

...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 ...omewhere around Fedora 9. It just seemed the distribution that served as a testing ground for Red Hat Enterprise Linux was too much work to get stable and too

...s goes well, we'll use it for F36. [https://ask.fedoraproject.org/t/we-are-testing-a-new-common-issues-category-and-process/18916 Your feedback] is welcome! {{Common bugs update testing|FEDORA-2021-f7d19c8901}}

...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 ...validation. In the mean time builds will continue to be pushed to updates-testing for 13, and even to 13 stable, however critical path packages might not be

...politique de mise à jour —, migrent du dépôt [[#updates-testing|''updates-testing'']] vers ce dépôt. ...itique de mise à jour]] migrent du dépôt [[#updates-testing|the ''updates-testing'']] vers ce dépôt. Cette différence d’avec "Branched" résulte de la n

...er packages against this. Bob shares his gtk2newness copr with others for validation of the new GTK2 ...ber of other packages with this rpm. Jill shares her rpm copr for further testing of the rpm change.

| image = [[File:Echo-testing-48px.png|link=QA/Fedora_22_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

| image = [[File:Echo-testing-48px.png|link=QA/Fedora_21_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

Enable the use of fsverity for installed RPM files validation. ...oes not appear to meaningfully slow down package installs during empirical testing. Once generated, the Merkle tree will use up some disk space for its storag

...de-redhat, and the availability of KDE SC 4.4rc2 live images available for testing. That rounds out FWN 212 -- read on! ...ture for the release are '''significantly''' "feature complete", ready for testing, and have a current status.<ref>https://fedoraproject.org/wiki/Feature_Free

'''Testing and Expected Results''' ** Issue different types of certificates like user certs, server certs

FreeIPA with integrated DNS server will support serving of DNSSEC secured zones and automatic DNSSEC key maint DNS server integrated to FreeIPA in Fedora 20 is not able to serve signed DNS zones. N

...the date? | If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test, fi The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:

* Live CD testing was introduced in [[QA/TestResults/Fedora9LiveCD/FinalRelease]] (and droppe * The ''Cloud'' and ''Server'' test types first appeared in [[:Category:Fedora_21_Alpha_Test_Results|Fed

...6 Alpha prep, oVirt node spin review and testing, and Instalatron anaconda testing framework details, to name but a few items. Security Advisories brings us ==== Outage: Server reboots - 2011-08-01 14:00 UTC ====

...h of the files and do your work there. Then after you've done appropriate testing, you can merge those changes into the branch you retrieved and send them to ...ges you made to the Release Notes produce a fully working document. Run a validation test to check (this example is using the original "en-US" language):

...ent in Greece. In Quality Assurance news, details on the latest Fedora 13 testing processes and results, and reports on two Test Days on Preupgrade Kit and X 2.6.35/2.6.36 kernel, GCC 4.5, and X.Org Server 1.9."

== AutoQA initscripts test validation == * jlaska - set up testing instance of autotest-server

...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 ...n tests as possible. James noted that he planned to bring the installation testing SOP<ref>http://fedoraproject.org/wiki/User:Liam/Draft_Install_Test_SOP</ref

* Storage validation * There was a SNAFU with fedup on release day: fedup 0.8 was still in updates-testing for F18 and F19 on the day of release, and it turned out upgrades to F20 wi

...lity Assurance reports on the latest Test Day on World IPv6, Security spin testing, and lots of other projects ongoing with Fedora 15 and 16. Security Adviso that are interested in testing this in advance, we have already updated

...ectures/ARM/qa-machines]] lists remotely-accessible machines available for testing purposes ...with running autotest on ARM hosts on Fedora 18: we agreed that automated testing on ARM should not blocker primary arch elevation as we are not enforcing th

...has completed. From the wiki pages, there were 26 bugs identified during testing. Alpha RC#1 is available for testing. Instructions for downloading and providing feedback available at:

...esign beat, updated details on Fedora 13 artwork including wallpapers, and testing results of the new Design Suite spin. Security Advisories provides last we The CVS server will not accept connections so that we can mass-branch for Fedora 13.

...i upgraded to 1.14.0. [https://pagure.io/modularity/issue/60, #60] Modular server replicated to mirrors correctly. [https://pagure.io/releng/issue/7056, #705 ...//pagure.io/fedora-infrastructure/issue/6182, #6182] The On Demand Compose Server (ODCS) needs to be deployed. Once the changes to the OSBS components (atomi

Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

...ery important, and we need your help. The Live image for CD and USB makes testing easy and painless, and improvements in virtualization make a full installat ...g a solid Fedora 11 release. You can make the Fedora 11 release better by testing the Beta release and reporting your findings.