From Fedora Project Wiki

Revision as of 16:19, 4 May 2016 by Kushal (talk | contribs) (Updating the page with more details and links to the test day webapp)

Fedora Test Day
Echo-testing-48px.png
FIXME

Date 2016-05-10
Time all day

Website QA/Test Days
IRC #fedora-test-day (webirc)

Mailing list
MailSubscribeArchives


Note.png
Can't make the date?
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, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's instalment of Fedora Test Day will focus on Cloud, Atmoic images for Fedora 24.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

You will require at least a system with libvirt/kvm installed. Having access to any Openstack or other Cloud IAAS system where you can upload an image will be even better.

Download the images from below links

  • Cloud Image link
  • Atomic Image link

Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:

How to test?

High level details on how a contributor can get involved. This can include (but not limited to):

  • Areas to target with exploratory testing
  • A list of pre-defined test cases to execute
  • How to report back results


Run the tests

Visit the result page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.

Exploratory testing

If you run out of test cases, congratulations! But that's not the end! You can still help out by playing around with the tool in whatever ways you can think of: try out all the things you can find, and try writing different Fedora images with it. If you have systems with different Windows versions, try running the tool on all of them. Get creative! Any problems you find please file a bug, or report to the IRC channel.

Reporting bugs

Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:

If you have problems with any of the tests, report a bug to Bugzilla usually for the component [List of components] If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.

Test Results

Please enter your results on the result page. The results will be transferred here after the Test Day is finished.