From Fedora Project Wiki

No edit summary
Line 22: Line 22:
* Quality Assurance - [[User:dmossor|Dan Mossor]] (danofsatx)
* Quality Assurance - [[User:dmossor|Dan Mossor]] (danofsatx)
* General Help - [[User:Simo|Simo Sorce]] (simo)
* General Help - [[User:Simo|Simo Sorce]] (simo)
* Test Day Organizer and Tester - [[User:Junland|John Unland]] (junland)

== Prerequisite for Test Day ==  
== Prerequisite for Test Day ==  

Revision as of 18:52, 6 November 2014

Fedora 21 Server Test Day

Date November 7th, 2014
Time all day

Website QA/Fedora_21_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 will be focusing on features of Rolekit, freeIPA, cockpit, and openLMI. We will be also testing for basic functionality. Please submit your findings to the table below.

Who's available

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

Prerequisite for Test Day

  • Extra Hard Disk Space
  • Virtualbox, QEMU, or VMWare Player
  • IRC Client (Optional)
  • x86 / x86-64 / ARM Hardware (Optional)

How to test?

  • Download Image for your particular Architecture.
  • Verify image through MD5 or SHA256 SUM. (VERY IMPORTANT)
  • Install Image on USB / DVD if you are testing on physical hardware.
  • Install image in a Virtual Machine or Physical Hardware.
  • Run through test cases.
  • Submit bugs / results in the table below.

Testing Image

Testing image can be found here: Fedora 21 Server Beta TC4

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. FreeIPA_Test_Cases|FreeIPA Test Cases

User Sample test 1 Sample test 2 Sample test 3 Sample test 4 References
Sample User
Pass pass
Warning warn
Fail fail
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345