Test Day:2016 05 10 Cloud: Difference between revisions

Revision as of 16:19, 4 May 2016

Fedora Test Day

FIXME

Date	2016-05-10
Time	all day

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

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 ...

Development - Kushal (kushal), Developer2 (irc_nick2)
Quality Assurance - Tester1 (irc_nick3), Tester2 (irc_nick4)

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:

An updated Fedora 24 nightly Cloud/Atomic image

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.

@@ Line 44: / Line 44: @@
+=== Run the tests ===
-=== Run the tests ===
+Visit the [http://testdays.fedorainfracloud.org/events/7 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.
-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.:
+=== Exploratory testing ===
-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.
+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 ==
@@ Line 55: / Line 56: @@
 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 [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.
+If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com 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 ==
-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/7 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/>
-|-
-|}
 [[Category:Fedora 24 Test Days]]
 <!-- remove this category when creating a test day page -->
 [[Category:QA Templates]]

Search