From Fedora Project Wiki

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 19: Line 19:


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:rcritten|Rob Crittenden]] (rcrit), [[User:puiterwijk|Patrick Uiterwijk]] (puiterwijk), [[User:simo|Simo Sorce]] (simo), [[User:nkinder|Nathan Kinder]] (nkinder)
* Development - [[rcritten:Rob Crittenden]] (rcrit), [[puiterwijk:Patrick Uiterwijk]] (puiterwijk), [[simo:Simo Sorces]] (simo), [[nkinder:Nathan Kinder]] (nkinder)
* QA - [[User:Roshi | Mike Ruckman]] (roshi)


== Prerequisite for Test Day ==  
== Prerequisite for Test Day ==  
Line 26: Line 25:
At least three virtual (or physical) machines will be required to test.
At least three virtual (or physical) machines will be required to test.


Recommendation is 1GB RAM and 4GB free disk post-install per-VM (a 10GB disk for the IDP/IPA and an 8 GB disk for each of the SP is fine).
Recommendation is 1GB RAM and 4GB free disk post-install per-VM.


Working DNS is required. It can be configured during the test.
Working DNS is required. It can be configured during the test.


You'll also need [https://getfedora.org/en/server/prerelease/ Fedora 22 Alpha].
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
 
* An updated [http://fedoraproject.org/get-prerelease Fedora 22 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 50: Line 51:
=== '''Update your machine''' ===
=== '''Update your machine''' ===


If you're running Fedora 22, make sure you have all the current updates for it installed, using the update manager.
If you're running Fedora 22, 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:
 
=== '''Configure the COPR repo''' ===
 
A few last-minute changes were made to the packages for the Test Day. Run:
 
# dnf copr enable rcritten/ipsilon
 
to enable the repository containing the needed packages before you begin testing.
 
=== '''Permissive SELinux''' ===
 
There are some known issues with SELinux at the moment. Please put each VM into permissive mode before proceeding with testing:
 
# setenforce permissive
 
At the completion of testing it would be great to get the output of:


# ausearch -m AVC -ts recent
=== '''Live image''' ===


for each VM.
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].


== Test Cases ==
== Test Cases ==
Line 83: Line 68:
SAML SP testing:
SAML SP testing:


* [[QA:Testcase_ipsilonv1_ipa_login|Test login/logout to SP]]
# Test login to SP
# Test logout from SP


Info plugin testing:
Info plugin testing:


* [[QA:Testcase_ipsilonv1_sssd_info|Test retrieving additional attributes]]
# Test retrieving additional attribute


Attribute mapping and filtering:
Attribute mapping and filtering:


* [[QA:Testcase_ipsilonv1_attr_map_filter|Map and filter attributes]]
# Map and filter attributes


== Test Results ==
FAS SP testing:


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=22&component=ipsilon ipsilon]. 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.
# Test login/logout of SP using FAS auth


If you get an Internal Server error on an SP then include in the bug report any errors you might find in {{filename|/var/log/httpd/ssl_error_log}}.
== Test Results ==


If you get an Internal Server error on the IDP then include in the bug report any errors you might find in {{filename|/var/log/httpd/error_log}}.
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:


Please include as much detail as you can on the steps taken to cause any exceptions.
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.


{|
{|
! User
! User
! [[QA:Testcase_ipsilonv1_ipa_install|Install IPA]]
! [[QA:Testcase_sample_1|Sample test 1]]
! [[QA:Testcase_ipsilonv1_ipa_idp_install|Install IDP]]
! [[QA:Testcase_sample_2|Sample test 2]]
! [[QA:Testcase_ipsilonv1_sp1_install|Install SPs]]
! [[QA:Testcase_sample_3|Sample test 3]]
! [[QA:Testcase_ipsilonv1_ipa_login|Login/out to SP]]
! [[QA:Testcase_sample_4|Sample test 4]]
! [[QA:Testcase_ipsilonv1_sssd_info|Info Plugins]]
! [[QA:Testcase_ipsilonv1_attr_map_filter|Attribute Mapping and Filtering]]
! References
! References
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:SampleUser|Sample User]]
| {{result|none}}
| {{result|none}}  
| {{result|none}}
| {{result|none}}
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
Line 122: Line 104:
| <references/>
| <references/>
|-
|-
|-
|}
| [[User:mrniranjan|mrniranjan]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>Logins pass but after logout and login back auth form doesn't come up instead it shows authenticated!</ref>
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
|-
| [[User:simo|simo]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>kdestory to test password based re-login</ref><ref>sometimes password-based re-login leaves me stranded in the Idp and does not redirect back - https://fedorahosted.org/ipsilon/ticket/74</ref><ref> Clicking on LogOut in the SP when user is already logged out in the Idp, gives a 400 - Bad Request in the Idp</ref>
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
|-
| [[User:spoore|spoore]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>same results as simo above</ref>
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
|-
| [[User:nkinder|nkinder]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>IdP initiated logout does not trigger SLO - https://fedorahosted.org/ipsilon/ticket/87</ref><ref>SP logout without an active session results in a 400 page - https://fedorahosted.org/ipsilon/ticket/88 (also encountered by simo and spoore above)</ref>
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
| [[User:Roshi|Roshi]]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|-
|-|}
 


[[Category:Fedora 22 Test Days]]
[[Category:QA Templates]]

Please note that all contributions to Fedora Project Wiki are considered to be released under the Attribution-Share Alike 4.0 International (see Fedora Project Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please solve the following task below and enter the answer in the box (more info):

Cancel Editing help (opens in new window)