From Fedora Project Wiki

(copy template)
 
(initial something)
Line 1: Line 1:
 
{{Infobox_group
 
{{Infobox_group
 
| name = Fedora Test Days
 
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]
+
| image = [[File:Echo-testing-48px.png|link=http://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day]]
| caption = [[FIXME|FIXME]]
+
| caption = [[Changes/Jenkins|Jenkins]]
| date = <<FIXME>>
+
| date = 2014-09-30
 
| time = all day
 
| time = all day
| website = [[QA/Fedora_19_test_days]]
+
| website = [http://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day Fedora Calendar ]
 
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
 
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
 
| fedora_mailing_list = test
 
| fedora_mailing_list = test
Line 14: Line 14:
 
== What to test? ==
 
== What to test? ==
  
Today's instalment of Fedora Test Day will focus on '''<<FIXME>>'''
+
Today's instalment of Fedora Test Day will focus on Jenkins. [https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins Read more]
  
 
== Who's available ==
 
== Who's available ==
  
 
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:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
+
* [[User:msrb|Michal Srb]] (msrb)
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
 
  
 
== Prerequisite for Test Day ==  
 
== Prerequisite for Test Day ==  
  
List any prerequisite needs for the test event.  A fresh system, virtualized guest, a blank DVD ... a desire to break software?
+
* bootable USB key or CD/DVD disk with latest Fedora 21 live image or:
 +
* machine or VM with updated Fedora 21
  
* Usb key
+
== Known issues ==
* 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:
+
TODO
 
 
* An updated [http://fedoraproject.org/get-prerelease Fedora XX pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
 
  
 
== How to test? ==
 
== How to test? ==
Line 45: Line 40:
 
Here's another common chunk (again, replace XX as above):
 
Here's another common chunk (again, replace XX as above):
  
=== '''Update your machine''' ===
+
=== Update your machine ===
  
If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
+
If you're running Fedora 21, make sure you have all the current updates for it installed, using the update manager.
  
=== '''Live image''' ===
+
=== 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].
+
The live images are suitable for writing to a USB stick or to a DVD media. They can be used for installing Fedora from scratch, and may also be used to test Fedora directly from the USB stick / DVD media without writing anything to your hard drive. More information on how to use the images is available at [[FedoraLiveCD]].
 +
 
 +
TODO - fix the links
 +
{|
 +
! Architecture !! SHA256SUM
 +
|-
 +
| [https://kojipkgs.fedoraproject.org//work/tasks/6453/7466453/Fedora-Live-Workstation-x86_64-21-20140827.iso 64 bit] || 8fce11269a8b1ea4283a3d4e3ecc78606d357f26de9efed248685c8c5be6c90d
 +
|-
 +
| [https://kojipkgs.fedoraproject.org//work/tasks/6450/7466450/Fedora-Live-Workstation-i686-21-20140827.iso 32 bit] || 8200c257514f0d302d62b54f68aae38179b83674c2e2dab4be9ba10090ce1ae3
 +
|}
  
 
== Test Cases ==
 
== 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]].
+
* '''Basic'''
 +
** [[Msrb:Testcase Jenkins start/stop|Jenkins start/stop]]
 +
 
 +
 
  
 
== Test Results ==
 
== 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 [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. 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.
 
  
 
{|
 
{|

Revision as of 13:15, 1 September 2014

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

Date 2014-09-30
Time all day

Website Fedora Calendar
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 Jenkins. Read more

Who's available

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

Prerequisite for Test Day

  • bootable USB key or CD/DVD disk with latest Fedora 21 live image or:
  • machine or VM with updated Fedora 21

Known issues

TODO

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

Here's another common chunk (again, replace XX as above):

Update your machine

If you're running Fedora 21, make sure you have all the current updates for it installed, using the update manager.

Live image

The live images are suitable for writing to a USB stick or to a DVD media. They can be used for installing Fedora from scratch, and may also be used to test Fedora directly from the USB stick / DVD media without writing anything to your hard drive. More information on how to use the images is available at FedoraLiveCD.

TODO - fix the links

Architecture SHA256SUM
64 bit 8fce11269a8b1ea4283a3d4e3ecc78606d357f26de9efed248685c8c5be6c90d
32 bit 8200c257514f0d302d62b54f68aae38179b83674c2e2dab4be9ba10090ce1ae3

Test Cases


Test Results

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