PyPi install tests fail

[GoogleCodeExporter]

What steps will reproduce the problem?
1. "pip install saml2idp"
2. setup django project and settings.py
3. "python manage.py test saml2idp"

What is the expected output? What do you see instead?
Tests should pass out-of-the-box. (Maybe. Think about this.)

Instead, there are several errors, dealing with an incomplete Django 
configuration, I think:

======================================================================
ERROR: test_deeplink (saml2idp.tests.deeplink.TestDeepLink)
ERROR: test_deeplink (saml2idp.tests.deeplink.TestDeepLinkWithAttributes)
ERROR: test_authnrequest_handled 
(saml2idp.tests.google_apps.TestGoogleAppsProcessor)
ERROR: test_user_logged_in (saml2idp.tests.google_apps.TestGoogleAppsProcessor)
ERROR: test_process_request_not_authorized 
(saml2idp.tests.views.TestLoginProcessView)
ERROR: test_empty_post (saml2idp.tests.views.TestLoginView)
ERROR: test_get (saml2idp.tests.views.TestLoginView)
ERROR: test_post (saml2idp.tests.views.TestLoginView)
ERROR: test_logout (saml2idp.tests.views.TestLogoutView)
ERROR: test_logout_user (saml2idp.tests.views.TestLogoutView)
ERROR: test_authnrequest_handled 
(saml2idp.tests.salesforce.TestSalesForceProcessor)
ERROR: test_user_logged_in (saml2idp.tests.salesforce.TestSalesForceProcessor)
----------------------------------------------------------------------
TemplateDoesNotExist: 404.html

======================================================================
ERROR: test_signed_assertion (saml2idp.tests.signing.TestAssertionSalesForce)
ERROR: test_signed_response_with_signed_assertion 
(saml2idp.tests.signing.TestResponse)
ERROR: test1 (saml2idp.tests.signing.TestSigning)
----------------------------------------------------------------------
KeyError: 'private_key_file'

-----------
Maybe these tests don't matter, but if people include 'saml2idp' in their 
INSTALLED_APPS, it might give them concern.

Original issue reported on code.google.com by [email protected] on 5 Jul 2012 at 4:41

[GoogleCodeExporter]

Adding the saml2idp urls to the project urls solves a lot.
Specifying paths to the sample certificate and key files solves a few more.
Still some trouble with a couple, so it's not all settings-related.

A clean checkout of the entire code is the preferred way to run tests. How many 
integrators will run tests on this library? (Even the Django tests don't always 
pass out-of-the-box.)

Original comment by [email protected] on 5 Jul 2012 at 4:58

• Added labels: ****
• Removed labels: ****