From Fedora Project Wiki
Fedora Test Days

Date 2013-06-06
Time all day

Website QA/Fedora_19_test_days
IRC #fedora-test-day (webirc)

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 FreeIPA Two Factor Authentication.

Who's available

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


We need your feedback!

Prerequisite for Test Day

  • A live image. Tips on using a live image are available at FedoraLiveCD.
Architecture SHA256SUM
x86_64 TODO
i686 TODO
Please make sure that the LiveCD has enough memory to operate. We recommend:
  • At minimum 2.5 GB of memory for non-graphical run
  • At minimum 3 GB memory for graphical (GNOME) run
  • Fedora 19 prepared with the following instructions:

# REQUIRED: Install FreeIPA
yum update
yum install freeipa-server freeipa-client sssd python-qrcode python-pyrad
systemctl start ipa-otpd.socket

# REQUIRED: Install testing environment
pushd /usr/local/sbin
chown root:root ipa-testday-otp ipa-testday-radius
chmod 755 ipa-testday-otp ipa-testday-radius

# OPTIONAL: simulated RADIUS daemon
pushd /usr/local/libexec
chown root:root ipa-testday-radiusd
chmod 755 ipa-testday-radiusd
pushd /lib/systemd/system
chown root:root ipa-testday-radiusd.service ipa-testday-radiusd.socket
chmod 644 ipa-testday-radiusd.service ipa-testday-radiusd.socket
systemctl start ipa-testday-radiusd.socket

# OPTIONAL: After testing, remove test environment and RADIUS daemon
rm -f /usr/local/sbin/ipa-testday-*
rm -f /usr/local/libexec/ipa-testday-radiusd
rm -f /lib/systemd/system/ipa-testday-radiusd.*

Test Cases

Install/Setup Tests:

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 freeipa, or krb5. 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.

User Basic installation tests Internal OTP External OTP Other References
Sample User
Pass pass
Warning warn
Fail fail
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345