|Cloud/Atomic Test Day|
What to test?
Today's instalment of Fedora Test Day will focus on Fedora Atomic and Cloud images
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
Prerequisite for Test Day
A fresh system (for Fedora Atomic Host), testcloud to test qcow images locally, or access to a cloud provider like OpenStack or AWS ... a desire to break software?
Fedora Atomic Host (FAH)
FAH can be run as a traditional cloud image, or installed to bare metal. If you have a spare machine you can install FAH to, please test this FIXME with link to FAH installer ISO. Download the image, write it to a USB stick and install like any other Fedora deliverable. If you need help, please ping in IRC.
The Fedora Cloud base image and Atomic images are also delivered as qcow2 images. You can use testcloud to locally boot and test either of these images. You can run testcloud from a git checkout, or use dnf to install it:
sudo dnf install testcloud
- Once it's installed, you can run testcloud like so:
testcloud instance create <name of instance> -u <url to qcow image>
How to test?
This testday is more general, so attempt to do anything and everything with these images :) Specifically though, we'd like to take a look at the following scenarios:
- Deploy applications on top of Atomic
- Upgrades and downgrades of existing Atomic Hosts (preferably with applications running)
- Test different cloud-init configs
- Package layering with on top of the base Atomic OSTree
Run the tests
If not using the Test Day app, provide a list of test areas or test cases that you'd like contributors to execute. For examples, see Category:Test_Cases. If using the Test Day app, link to it here, with some explanation, e.g.:
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.
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.
If you use the Test Days app, just explain that users should enter results there and they will be transferred to the page later. For e.g.:
Please enter your results on the result page. The results will be transferred here after the Test Day is finished.
Otherwise, 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 text to explain reporting. Here is a common setup:
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|