From Fedora Project Wiki

Line 36: Line 36:
 
== How to test? ==
 
== How to test? ==
  
High level details on how a contributor can get involved. This can include (but not limited to):
+
Ipsilon has a number of different components. Multiple virtual machines (or physical machines if you'd prefer) will be necessary to test.
  
* Areas to target with exploratory testing
+
Testing will involve:
* A list of pre-defined test cases to execute
+
* Installing an identity source (IPA)
* How to report back results
+
* Installing an Identity Provider (IDP)
 +
* Installing one or more Service Providers (SP)
 +
* Testing login and logout between those service providers using a browser.
  
Here's another common chunk (again, replace XX as above):
+
See below for specific details.
  
 
=== '''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 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:
  
 
=== '''Live image''' ===
 
=== '''Live image''' ===

Revision as of 16:14, 5 March 2015

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

Date 2015-03-12
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 installment of Fedora Test Day will focus on Ipsilon. Ipsilon is a server and a toolkit to configure Apache-based Service Providers. The server is a plugable self-contained mod_wsgi application that provides federated SSO to web applications. User authentication is always performed against a separate Identity Management system (for example a FreeIPA server), and communication with applications is done using a federation protocol like SAML, OpenID, etc..

Who's available

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

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?

  • Usb key
  • 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:

How to test?

Ipsilon has a number of different components. Multiple virtual machines (or physical machines if you'd prefer) will be necessary to test.

Testing will involve:

  • Installing an identity source (IPA)
  • Installing an Identity Provider (IDP)
  • Installing one or more Service Providers (SP)
  • Testing login and logout between those service providers using a browser.

See below for specific details.

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 want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

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 here.

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.

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.

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