From Fedora Project Wiki

Line 38: Line 38:
== How to test? ==
== How to test? ==


High level details on how a contributor can get involved. This can include (but not limited to):
We need to test several things on the Fedora Atomic release before Fedora 21 Final.  


* Areas to target with exploratory testing
* Test with a variety of Docker images. We do want to test the Fedora images in particular, but also we need to test a wide variety of images to see if there are any hidden bugs or problems we might not have noticed yet.
* A list of pre-defined test cases to execute
* Test Cockpit to make sure that managing Docker images and connecting multiple hosts works.
* How to report back results
* Try out Kubernetes and make sure those packages are working.
 
* Test out the rpm-ostree/atomic update/rollback commands and other functions.
Here's another common chunk (again, replace XX as above):
* What is the image/package set missing? What is unnecessary?


=== '''Grab the Image''' ===
=== '''Grab the Image''' ===


To test Fedora Atomic, we're going to use a Koji build located here: [https://kojipkgs.fedoraproject.org//work/tasks/8904/8118904/Fedora-Cloud-Atomic-20141112-21.x86_64.qcow2]. You can also use one of the AMIs if you would prefer to do your testing on Amazon Web Services.
To test Fedora Atomic, we're going to use a Koji build located here: [https://kojipkgs.fedoraproject.org//work/tasks/8904/8118904/Fedora-Cloud-Atomic-20141112-21.x86_64.qcow2]. You can also use one of the AMIs if you would prefer to do your testing on Amazon Web Services.
=== '''Live image''' ===
Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].


== Test Cases ==
== Test Cases ==

Revision as of 10:03, 17 November 2014

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

Date 20 November 2014
Time all day

Website QA/Fedora_21_test_days
IRC #atomic (webirc)
Mailing list cloud


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 Fedora Atomic Host

Who's available

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

Prerequisite for Test Day

You'll need to either have an AWS account or a system that's capable of running one of the Atomic images for KVM/OpenStack.

  • Usb key
  • Usb externally connected HD IDE/SATA
  • Empty HD IDE/SATA/SCSI
  • Free space on HD

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

How to test?

We need to test several things on the Fedora Atomic release before Fedora 21 Final.

  • Test with a variety of Docker images. We do want to test the Fedora images in particular, but also we need to test a wide variety of images to see if there are any hidden bugs or problems we might not have noticed yet.
  • Test Cockpit to make sure that managing Docker images and connecting multiple hosts works.
  • Try out Kubernetes and make sure those packages are working.
  • Test out the rpm-ostree/atomic update/rollback commands and other functions.
  • What is the image/package set missing? What is unnecessary?

Grab the Image

To test Fedora Atomic, we're going to use a Koji build located here: [1]. You can also use one of the AMIs if you would prefer to do your testing on Amazon Web Services.

Test Cases

Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases.

Test Results

Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. 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 udisks, or gnome-disk-utility for bugs in the Palimpsest graphical front end itself. 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. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.

User Sample test 1 Sample test 2 Sample test 3 Sample test 4 References
Sample User
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345