|Tuesday March 30, 2010||ALL DAY||#fedora-test-day (webirc)|
What to test?
Today's installment of Fedora Test Day will focus on SSSD by default
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test with your system and provide feedback.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion...
- Development - Stephen Gallagher, Simo Sorce, Tomas Mraz
- Quality Assurance - User:jgalipea, User:zmraz, User:gowrishankar
- Design - Máirín Duffy
What's needed to test
- A system with a network connection
- Fedora 13 (Branched) (tips on installing Branched below) with
installed, or a SSSD live image
How to test?
Before executing the test cases, you need to install and configure sssd. The necessary steps are outlined on the SSSD installation page. If you are using the Test Day live image, the installation steps will be completed for you.
Update your machine
See the instructions on the Branched page on the various ways in which you can install or update to the Branched release. Be sure you are testing with the latest authconfig-6.1.2-1.fc13. To install the latest
yum --enablerepo=updates-testing update authconfig
When ready, please follow each of these test cases:
Report your Results
If you have problems with any of the tests, report a bug to Trac. If you are unsure about exactly how to file the report, 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 James Laska 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, if your system worked correctly, simply enter the word
PASS. If you had trouble, enter the word
FAIL, with a link to the bug report for the failure. If you could not perform one test (for example, you cannot perform the more advanced tests because the basic one fails, or you cannot perform the private LDAP test as you do not have access to an LDAP server), enter the word N/A. In the comments column, you can enter any short, additional information about your testing environment.