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

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

...5350.html Proposed 2012-02-01], [https://lists.fedoraproject.org/pipermail/test/2012-February/105677.html implemented 2012-02-20] ...d=293093 Re-worded 2012-06-29], [https://lists.fedoraproject.org/pipermail/test/2012-October/111098.html extended 2012-10-24], and re-written again for maj

...5350.html Proposed 2012-02-01], [https://lists.fedoraproject.org/pipermail/test/2012-February/105677.html implemented 2012-02-20] ...d=293093 Re-worded 2012-06-29], [https://lists.fedoraproject.org/pipermail/test/2012-October/111098.html extended 2012-10-24], and re-written again for maj

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

...ptical support 2016-12-06], [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/HLXHEB364LOLFHB2RDX6K4DFA4VJIWMF/ implementa Test cases:

...ptical support 2016-12-06], [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/thread/HLXHEB364LOLFHB2RDX6K4DFA4VJIWMF/ implementa Test cases:

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

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

''Summary of idea:'' Every package that is included into Fedora needs to go through a review to ensure it matc * Make Fedora Review PEP8 compliant, fix its current test cases

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

There are some applications like Cockpit which we would like to ship as layered applications. ...as possible, allowing for local users or products to override this base in cases they need to do so.

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | website = [[QA/Test Days]]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

| name = Upgrade Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

..._Pre_Release|complete]] test release: Beta is the last widely co-ordinated test release point in any given release cycle ...6531.html Proposed 2013-06-21], [https://lists.fedoraproject.org/pipermail/test/2013-July/116738.html implemented 2013-07-02]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

| name = Fedora Test Day | image = [[File:Echo-testing-48px.png|link=QA/Test Days]]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

...lso important to allow Fedora packagers to locally and manually invoke a ''test suite''. ...playbooks in the <code>tests/</code> folder that can be invoked to run the test suites.

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * Test case: [[QA:Testcase_base_edition_self_identification]]

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/EFTMMXJYAZOW5CHBCON6UHWCUYWF34OY/ Council w

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/EFTMMXJYAZOW5CHBCON6UHWCUYWF34OY/ Council w

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/EFTMMXJYAZOW5CHBCON6UHWCUYWF34OY/ Council w

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/EFTMMXJYAZOW5CHBCON6UHWCUYWF34OY/ Council w

* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/CPRQ6UJMMADQAUYTHCDKNOROINGOOHRH/ proposed * [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/EFTMMXJYAZOW5CHBCON6UHWCUYWF34OY/ Council w

For example: This change allows package upgrades to be performed automatically and rolled-back at will. Does this improve some specific package or set of packages?

...g for nightlies (qa / releng) to match more closely the RC (qa / releng / test-days) ...Atomic_Developer_Mode Developer Mode]''', the host will download and start Cockpit and fire up a '''tmux''' session to make it easier to work at the console a

* changes to isolated/leaf package without the impact on other packages/rest of the distribution ...n the operating system and what the user has installed on top of it; if we package software as xdg-app bundles depending on a standard runtime or as Docker co

| name = Upgrade Test Day | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]

...|| {{question}} || {{check}} || {{check}} || QQS (London) <=> BRU || en || Package Maintainer ...|| {{check}} || {{check}} || {{check}} || VIE <=> BRU || en, cz || Python package Maintainer

...s after items in the rebuild line are how many other applications use that package. A high count means that it's a good candidate for flatpak-common in the fu ! !! Package !! Flathub ID !! # Reviews !! Avg. Review !! In progress?