From Fedora Project Wiki

Line 18: Line 18:
  
 
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
 
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:dustymabe|Dustymabe]] (irc_dustymabe)
+
* Development - [[User:dustymabe|Dustymabe]] (irc dustymabe)
* Quality Assurance - [[User:Roshi|Roshi]] (irc_roshi)
+
* Quality Assurance - [[User:Roshi|Roshi]] (irc roshi)
  
 
== Prerequisite for Test Day ==  
 
== Prerequisite for Test Day ==  
Line 36: Line 36:
 
<code>
 
<code>
 
sudo dnf install testcloud
 
sudo dnf install testcloud
 +
</code>
  
 +
Once it's installed, you can run testcloud like so:
  
# Once it's installed, you can run testcloud like so:
+
<code>
 
testcloud instance create <name of instance> -u <url to qcow image>
 
testcloud instance create <name of instance> -u <url to qcow image>
 
</code>
 
</code>
Line 47: Line 49:
 
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:
 
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:
  
 +
'''Atomic:'''
 
* Deploy applications on top of Atomic
 
* Deploy applications on top of Atomic
 
* Upgrades and downgrades of existing Atomic Hosts (preferably with applications running)
 
* 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
 
* Package layering with on top of the base Atomic OSTree
  
 +
'''Cloud:'''
 +
* Test different cloud-init configs
 +
* Deploy and run some applications in the cloud
  
 
=== Run the tests ===
 
=== 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 [http://testdays.fedorainfracloud.org/events/NUMBER 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.
  
Visit the [http://testdays.fedorainfracloud.org/events/NUMBER 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.
+
This testday is also meant to be exploratory, so the list on the testday app is not at all comprehensive!
  
 
== Reporting bugs ==
 
== 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 find anything that seems wrong or off, please report a bug on [https://bugzilla.redhat.com Bugzilla]. The affected component should be clear from whatever error message you happen to find, but if you aren't sure what component to file against, please file it against '''FIXME'''. 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 have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility 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.
 
  
 
== Test Results ==
 
== Test Results ==
 
If you use the [http://testdays.fedorainfracloud.org/events 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 [http://testdays.fedorainfracloud.org/events/NUMBER result page]. The results will be transferred here after the Test Day is finished.
 
Please enter your results on the [http://testdays.fedorainfracloud.org/events/NUMBER 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 [[Template:result|result template]] to enter your result, as shown in the example result line.
 
{|
 
! User
 
! [[QA:Testcase_sample_1|Sample test 1]]
 
! [[QA:Testcase_sample_2|Sample test 2]]
 
! [[QA:Testcase_sample_3|Sample test 3]]
 
! [[QA:Testcase_sample_4|Sample test 4]]
 
! References
 
|-
 
| [[User:SampleUser|Sample User]]
 
| {{result|none}}
 
| {{result|pass}}
 
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
 
| {{result|fail}} <ref>{{bz|12345}}</ref>
 
| <references/>
 
|-
 
|}
 

Revision as of 14:45, 9 June 2017

Cloud/Atomic Test Day
Test-days-banner.svg

Date 2017-06-20
Time all day

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


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 and Cloud images

Who's available

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

  • Development - Dustymabe (irc dustymabe)
  • Quality Assurance - Roshi (irc roshi)

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.

Qcow2 images

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:

Atomic:

  • Deploy applications on top of Atomic
  • Upgrades and downgrades of existing Atomic Hosts (preferably with applications running)
  • Package layering with on top of the base Atomic OSTree

Cloud:

  • Test different cloud-init configs
  • Deploy and run some applications in the cloud

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.

This testday is also meant to be exploratory, so the list on the testday app is not at all comprehensive!

Reporting bugs

If you find anything that seems wrong or off, please report a bug on Bugzilla. The affected component should be clear from whatever error message you happen to find, but if you aren't sure what component to file against, please file it against FIXME. 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.