Testing

1 Profile Flow Unit Tests
2 Eclipse Testbed
- 2.1 Properties
- 2.2 Logging
- 2.3 Storage
  - 2.3.1 web.xml
- 2.4 Troubleshooting Eclipse Testbed
  - 2.4.1 ClassNotFoundException
3 Integration Tests

Profile Flow Unit Tests

The idp-conf Maven module, which includes most of the as-delivered configuration files that end up in the distribution, includes TestNG unit tests that exercise many of the webflows, but without using a browser (so just programmatically with mock objects).

The tests extend AbstractFlowTest, which is responsible for :

Creating mock objects such as HttpServletRequest, HttpServletResponse, and the Spring Web Flow ExternalContext
Overriding flows to return the OpenSAML ProfileRequestContext as a Spring Web Flow output attribute

Tests of SAML flows extract the SAML Response from the OpenSAML ProfileRequestContext and validate the Response using a validator, for example the SAML2TestResponseValidator.

Eclipse Testbed

The java-idp-testbed project is a stand-alone project that runs the IdP inside Eclipse (programmatically starting Jetty as the container). The code being run is the code in Eclipse under active development, so it's possible to test changes to all of the libraries or third party extensions in-situ.

A very simple mock SP included in the testbed simply displays the messages it receives for diagnostic purposes and it can initiate SAML profiles in various ways.

The testbed provides :

an IdP configured by idp-conf from the classpath (by setting the idp.home and idp.webflows system properties)
a mock SAML SP
a test in-memory LDAP directory server

Properties

Note that the Jetty WebAppProvider configured in idp-jetty-base's jetty-deploy.xml reads properties from idp-jetty-base's start.d/idp.ini, hence properties used in a deployment descriptor XML file are not overridable via command line arguments or via other start.d/*.ini files.

Logging

Jetty will log to ${workspace_loc:idp-jetty-base}/src/main/resources/jetty-base/logs

The IdP will log to ${workspace_loc:idp-jetty-base}/src/main/resources/jetty-base/classpath/logs

To log to the Eclipse console :

comment out --module=logging in ${workspace_loc:idp-jetty-base}/src/main/resources/jetty-base/start.ini
add <include resource="conf/logback-include-console.xml" /> to the end of ${workspace_loc:idp-conf}/src/main/resources/conf/logback.xml (this includes ${workspace_loc:idp-conf}/src/test/resources/conf/logback-include-console.xml)

Storage

To interact with IdP storage services via HTTP, add the following to idp-war/src/main/webapp/WEB-INF/web.xml :

web.xml

<!-- The /storage app space. Interact with storage services via HTTP. -->
<servlet>
    <servlet-name>storage</servlet-name>
    <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
    <init-param>
        <param-name>contextConfigLocation</param-name>
        <param-value>classpath:/system/conf/storage-context.xml</param-value>
     </init-param>
     <load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
    <servlet-name>storage</servlet-name>
    <url-pattern>/storage/*</url-pattern>
</servlet-mapping>

See the Javadoc for the testbed StorageServiceWrapperController for usage.

Troubleshooting Eclipse Testbed

ClassNotFoundException

If Eclipse can not find Jetty classes :

WARNING: Nothing to start, exiting ...
java.lang.ClassNotFoundException: org.eclipse.jetty.xml.XmlConfiguration

make sure that the version of Jetty specified via jetty.home and the testbed POM match.

-Djetty.home=/opt/jetty/jetty-distribution-9.3.16.v20170120

<jetty.version>9.3.16.v20170120</jetty.version>

Integration Tests

The java-idp-integration-tests project exercises profile flows using a browser via Selenium.

The tests configure and run the IdP and testbed web apps. The SAML assertion produced by the IdP and received by the testbed SP is retrieved by the browser and validated using the same validator used by the idp-conf tests.

See How to Run IdP Browser/Integration Tests for further information.

Identity Provider 5