| Fedora Test Days | |
|---|---|
| |
| FIXME | |
| Date | 20 November 2014 |
| Time | all day |
| Website | QA/Fedora_21_test_days |
| IRC | #atomic (webirc) |
| Mailing list | cloud |
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 ...
- Cloud SIG - Joe Brockmeier (jzb)
- Development - Developer1 (irc_nick1), Developer2 (irc_nick2)
- Quality Assurance - Tester1 (irc_nick3), Tester2 (irc_nick4), Tester3 (irc_nick5)
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.
- OpenStack installation [outside the scope of test day to set up!]
- Virt-Manager or KVM setup to run the qcow2 image.
- An updated test image, or later nightly live image if one is released before 20 November.
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 |  |
 |
 |