Search results

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

Practically, there are only two use cases that currently justify usage of “files provider”: For both cases “proxy provider” is a viable substitute, so “files provider” can be

| name = Fedora Test Days ...the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}

...elease installable media versions of a [[Changes/Policy|feature complete]] test release # Test [[Releases/21/ChangeSet|accepted Changes of {{FedoraVersion|long|21}}]]

| name = Fedora Test Days ...the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}

...elease installable media versions of a [[Changes/Policy|feature complete]] test release # Test [[Releases/22/ChangeSet|accepted Changes of {{FedoraVersion|long|22}}]]

...It is also important to allow packagers to locally and manually invoke a ''test suite''. Each dist-git repo that has integration tests should package those tests in one or more subpackages

...elease installable media versions of a [[Changes/Policy|feature complete]] test release # Test [[Releases/23/ChangeSet|accepted Changes of {{FedoraVersion|long|23}}]]

...elease installable media versions of a [[Changes/Policy|feature complete]] test release # Test [[Releases/24/ChangeSet|accepted Changes of {{FedoraVersion|long|24}}]]

...elease installable media versions of a [[Changes/Policy|feature complete]] test release # Test [[Releases/25/ChangeSet|accepted Changes of {{FedoraVersion|long|25}}]]

| name = Fedora Test Days ...the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i

...t cover users, who don’t have much experience with Linux partitioning (use cases as reinstall my existing system). Another issue is that the Anaconda team s **** It is simple and should cover a lot of cases in a simple way.

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i

...elease installable media versions of a [[Changes/Policy|feature complete]] test release # Test [[Releases/26/ChangeSet|accepted Changes of {{FedoraVersion|long|26}}]]

...s all the composes for the current release: it can help you see which test cases most need to be run.}} ...sts for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not bee

* This needs to work with Yum/DNF, MicroDNF, PackageKit, Cockpit, rpm-ostree, GNOME Software, Muon, Apper, and software update mechanisms us ...to distinguish between short-lived instances (like temporary containers or test machines) and actual installations.

# Publicly release installable media versions of a test release # Test accepted Changes for future releases

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle * [https://lists.fedoraproject.org/pipermail/test/2011-April/098811.html Proposed 2011-04-11], [https://fedoraproject.org/w/i