Search results

...fy enough, the Alpha release of Fedora 18 is even meatier. Anyone can help test this release, guided by the [[QA|Fedora QA team]], which helps us identify === Cloud and Virtualization ===

= Build Fedora Cloud Edition Images Using Kiwi in Koji = ...agefactory ImageFactory] tooling that is currently being used to build the cloud base images.

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

...nstall your own instance of openQA so you can try it out and contribute to test development. ...-level testing. Its key feature is that it interacts with the system under test much like a human would, by sending input using a virtual keyboard and mous

* Test Days ...ecided that it doesn't make sense to do this with the current app. current cloud setup is OK for now

| name = Fedora Test Days | caption = OpenStack Test Day

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

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

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) We are working on scratch gcc rpms and will perform a test mass rebuild.

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...es selecting some of the rules (or groups of rules) targetting various use cases.

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) We are working on scratch gcc rpms and will perform a test mass rebuild.

<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) We are working on scratch gcc rpms and will perform a test mass rebuild.

= Test Day = We held a [[Test_Day:2012-03-08_OpenStack_Test_Day|test day for OpenStack Essex in Fedora 17 on March 8]].

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

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

...yslog, Syslog-NG, and even traditional sysklogd will continue to cover use cases outside of the default. ...e). This is significant on systems with limited resources, like the Fedora Cloud image.

...is page provides guidance on arranging and announcing a release validation test event. For any concerns, please contact the [[QA]] group. ...n/caution|This process is now automated|The creation of release validation test events is now automated. Wiki pages are created and an announcement email s

** old cloud modules, move to new 2.0 cloud management * Add a unit test suite to the-new-hotness.

...ng|Not current|The Default Offering was effectively replaced with separate Cloud/Server/Workstation editions as part the [[Fedora.next]].}} ...ees with the goal of attracting people to switch to a new OS -- offering a test drive is natural and helpful to the user.

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