keycloak-scim/testsuite/integration-arquillian/HOW-TO-RUN.md

How To Run various testsuite configurations

Base steps

It's recomended to build the workspace including distribution.

cd $KEYCLOAK_SOURCES
mvn clean install -DskipTests=true
cd distribution
mvn clean install

Debugging - tips & tricks

Arquillian debugging

Adding this system property when running any test:

-Darquillian.debug=true

will add lots of info to the log. Especially about:

• The test method names, which will be executed for each test class, will be written at the proper running order to the log at the beginning of each test class(done by KcArquillian class).
• All the triggered arquillian lifecycle events and executed observers listening to those events will be written to the log
• The bootstrap of WebDriver will be unlimited. By default there is just 1 minute timeout and test is cancelled when WebDriver is not bootstrapped within it.

WebDriver timeout

By default, WebDriver has 10 seconds timeout to load every page and it timeouts with error after that. Use this to increase timeout to 1 hour instead:

-Dpageload.timeout=3600000

Surefire debugging

For debugging, the best is to run the test from IDE and debug it directly. When you use embedded Undertow (which is by default), then JUnit test, Keycloak server and adapter are all in the same JVM and you can debug them easily. If it is not an option and you are forced to test with Maven and Wildfly (or EAP), you can use this:

-Dmaven.surefire.debug=true

and you will be able to attach remote debugger to the test. Unfortunately server and adapter are running in different JVMs, so this won't help to debug those.

JBoss auth server debugging

When tests are run on JBoss based container (WildFly/EAP) there is possibility to attach a debugger, by default on localhost:5005.

The server won't wait to attach the debugger. There are some properties what can change the default behaviour.

-Dauth.server.debug.port=$PORT
-Dauth.server.debug.suspend=y

More info: http://javahowto.blogspot.cz/2010/09/java-agentlibjdwp-for-attaching.html

JBoss app server debugging

Analogically, there is the same behaviour for JBoss based app server as for auth server. The default port is set to 5006. There are app server properties.

-Dapp.server.debug.port=$PORT
-Dapp.server.debug.suspend=y    

Testsuite logging

It is configured in testsuite/integration-arquillian/tests/base/src/test/resources/log4j.properties . You can see that logging of testsuite itself (category org.keycloak.testsuite) is debug by default.

When you run tests with undertow (which is by default), there is logging for Keycloak server and adapter (category org.keycloak ) in info when you run tests from IDE, but off when you run tests with maven. The reason is that, we don't want huge logs when running mvn build. However using system property keycloak.logging.level will override it. This can be used for both IDE or maven. So for example using -Dkeycloak.logging.level=debug will enable debug logging for keycloak server and adapter.

For more fine-tuning of individual categories, you can look at log4j.properties file and temporarily enable/disable them here.

TODO: Add info about Wildfly logging

Run adapter tests

Wildfly

# Prepare servers
mvn -f testsuite/integration-arquillian/servers/pom.xml clean install \
   -Pauth-server-wildfly \
   -Papp-server-wildfly

# Run tests
mvn -f testsuite/integration-arquillian/tests/other/adapters/jboss/wildfly/pom.xml \
   clean install \
   -Pauth-server-wildfly \
   -Papp-server-wildfly

JBoss Fuse 6.3

1. Download JBoss Fuse 6.3 to your filesystem. It can be downloaded from http://origin-repository.jboss.org/nexus/content/groups/m2-proxy/org/jboss/fuse/jboss-fuse-karaf Assumed you downloaded jboss-fuse-karaf-6.3.0.redhat-229.zip

2. Install to your local maven repository and change the properties according to your env (This step can be likely avoided if you somehow configure your local maven settings to point directly to Fuse repo):

   mvn install:install-file
   -DgroupId=org.jboss.fuse
   -DartifactId=jboss-fuse-karaf
   -Dversion=6.3.0.redhat-229
   -Dpackaging=zip
   -Dfile=/mydownloads/jboss-fuse-karaf-6.3.0.redhat-229.zip

3. Prepare Fuse and run the tests (change props according to your environment, versions etc):

   Prepare Fuse server

   mvn -f testsuite/integration-arquillian/servers
   clean install
   -Pauth-server-wildfly
   -Papp-server-fuse63
   -Dfuse63.version=6.3.0.redhat-229
   -Dapp.server.karaf.update.config=true
   -Dmaven.local.settings=$HOME/.m2/settings.xml
   -Drepositories=,http://download.eng.bos.redhat.com/brewroot/repos/sso-7.1-build/latest/maven/
   -Dmaven.repo.local=$HOME/.m2/repository

   Run the Fuse adapter tests

   mvn -f testsuite/integration-arquillian/tests/other/adapters/karaf/fuse63/pom.xml
   clean install
   -Pauth-server-wildfly
   -Papp-server-fuse63
   -Dfuse63.version=6.3.0.redhat-229

EAP6 with Hawtio

1. Download JBoss EAP 6.4.0.GA zip

2. Install to your local maven repository and change the properties according to your env (This step can be likely avoided if you somehow configure your local maven settings to point directly to EAP repo):

   mvn install:install-file
   -DgroupId=org.jboss.as
   -DartifactId=jboss-as-dist
   -Dversion=7.5.0.Final-redhat-21
   -Dpackaging=zip
   -Dfile=/mydownloads/jboss-eap-6.4.0.zip

3. Download Fuse EAP installer (for example from http://origin-repository.jboss.org/nexus/content/groups/m2-proxy/com/redhat/fuse/eap/fuse-eap-installer/6.3.0.redhat-220/ )

4. Install previously downloaded file manually

   mvn install:install-file
   -DgroupId=com.redhat.fuse.eap
   -DartifactId=fuse-eap-installer
   -Dversion=6.3.0.redhat-220
   -Dpackaging=jar
   -Dfile=/fuse-eap-installer-6.3.0.redhat-220.jar

5. Prepare EAP6 with Hawtio and run the test

   Prepare EAP6 and deploy hawtio

   mvn -f testsuite/integration-arquillian/servers
   clean install
   -Pauth-server-wildfly
   -Papp-server-eap6-fuse
   -Dapp.server.jboss.version=7.5.0.Final-redhat-21
   -Dfuse.installer.version=6.3.0.redhat-220

   Run the test

   mvn -f testsuite/integration-arquillian/tests/other/adapters/jboss/eap6-fuse/pom.xml
   clean install
   -Pauth-server-wildfly
   -Papp-server-eap6-fuse

Migration test

DB migration test

This test will:

• start Keycloak 1.9.8 (replace with the other version if needed)
• import realm and some data to MySQL DB
• stop Keycloak 1.9.8
• start latest Keycloak, which automatically updates DB from 1.9.8
• Do some test that data are correct

1. Prepare MySQL DB and ensure that MySQL DB is empty. See ../../misc/DatabaseTesting.md for some hints for locally prepare Docker MySQL image.

2. Run the test (Update according to your DB connection, versions etc):

   export DB_HOST=localhost

   mvn -f testsuite/integration-arquillian/pom.xml
   clean install
   -Pauth-server-wildfly,jpa,clean-jpa,auth-server-migration
   -Dtest=MigrationTest
   -Dmigration.mode=auto
   -Dmigrated.auth.server.version=1.9.8.Final
   -Djdbc.mvn.groupId=mysql
   -Djdbc.mvn.version=5.1.29
   -Djdbc.mvn.artifactId=mysql-connector-java
   -Dkeycloak.connectionsJpa.url=jdbc:mysql://$DB_HOST/keycloak
   -Dkeycloak.connectionsJpa.user=keycloak
   -Dkeycloak.connectionsJpa.password=keycloak

DB migration test with manual mode

Same test as above, but it uses manual migration mode. During startup of the new Keycloak server, Liquibase won't automatically perform DB update, but it just exports the needed SQL into the script. This SQL script then needs to be manually executed against the DB.

1. Prepare MySQL DB (Same as above)

2. Run the test (Update according to your DB connection, versions etc). This step will end with failure, but that's expected:

   mvn -f testsuite/integration-arquillian/pom.xml
   clean install
   -Pauth-server-wildfly,jpa,clean-jpa,auth-server-migration
   -Dtest=MigrationTest
   -Dmigration.mode=manual
   -Dmigrated.auth.server.version=1.9.8.Final
   -Djdbc.mvn.groupId=mysql
   -Djdbc.mvn.version=5.1.29
   -Djdbc.mvn.artifactId=mysql-connector-java
   -Dkeycloak.connectionsJpa.url=jdbc:mysql://$DB_HOST/keycloak
   -Dkeycloak.connectionsJpa.user=keycloak
   -Dkeycloak.connectionsJpa.password=keycloak

3. Manually execute the SQL script against your DB. With Mysql, you can use this command (KEYCLOAK_SRC points to the directory with the Keycloak codebase):

   mysql -h $DB_HOST -u keycloak -pkeycloak < $KEYCLOAK_SRC/testsuite/integration-arquillian/tests/base/target/containers/auth-server-wildfly/keycloak-database-update.sql

4. Finally run the migration test, which will verify that DB migration was successful. This should end with success:

   mvn -f testsuite/integration-arquillian/tests/base/pom.xml
   clean install
   -Pauth-server-wildfly
   -Dskip.add.user.json=true
   -Dmigrated.auth.server.version=1.9.8.Final
   -Dtest=MigrationTest

JSON export/import migration test

This will start latest Keycloak and import the realm JSON file, which was previously exported from Keycloak 1.9.8.Final

mvn -f testsuite/integration-arquillian/pom.xml \
  clean install \
  -Pauth-server-wildfly,migration-import \
  -Dtest=MigrationTest \
  -Dmigration.mode=import \
  -Dmigrated.auth.server.version=1.9.8.Final

UI tests

The UI tests are real-life, UI focused integration tests. Hence they do not support the default HtmlUnit browser. Only the following real-life browsers are supported: Mozilla Firefox, Google Chrome and Internet Explorer. For details on how to run the tests with these browsers, please refer to Different Browsers chapter.

The UI tests are focused on the Admin Console as well as on some login scenarios. They are placed in the console module and are disabled by default.

The tests also use some constants placed in test-constants.properties. A different file can be specified by -Dtestsuite.constants=path/to/different-test-constants.properties

Execution example

mvn -f testsuite/integration-arquillian/tests/other/console/pom.xml \
    clean test \
    -Dbrowser=firefox \
    -Dfirefox_binary=/opt/firefox-45.1.1esr/firefox

Welcome Page tests

The Welcome Page tests need to be run on WildFly/EAP and with -Dskip.add.user.json switch. So that they are disabled by default and are meant to be run separately.

# Prepare servers
mvn -f testsuite/integration-arquillian/servers/pom.xml \
    clean install \
    -Pauth-server-wildfly \
    -Papp-server-wildfly

# Run tests
mvn -f testsuite/integration-arquillian/tests/base/pom.xml \
    clean test \
    -Dtest=WelcomePageTest \
    -Dskip.add.user.json \
    -Pauth-server-wildfly

Social Login

The social login tests require setup of all social networks including an example social user. These details can't be shared as it would result in the clients and users eventually being blocked. By default these tests are skipped.

To run the full test you need to configure clients in Google, Facebook, GitHub, Twitter, LinkedIn, Microsoft and StackOverflow. See the server administration guide for details on how to do that. Further, you also need to create a sample user that can login to the social network.

The details should be added to a standard properties file. For some properties you can use shared common properties and override when needed. Or you can specify these for all providers. All providers require at least clientId and clientSecret (StackOverflow also requires clientKey).

An example social.properties file looks like:

common.username=sampleuser@example.org
common.password=commonpassword
common.profile.firstName=Foo
common.profile.lastName=Bar
common.profile.email=sampleuser@example.org

google.clientId=asdfasdfasdfasdfsadf
google.clientSecret=zxcvzxcvzxcvzxcv

facebook.clientId=asdfasdfasdfasdfsadf
facebook.clientSecret=zxcvzxcvzxcvzxcv
facebook.profile.lastName=Test

In the example above the common username, password and profile are shared for all providers, but Facebook has a different last name.

Some providers actively block bots so you need to use a proper browser to test. Either Firefox or Chrome should work.

To run the tests run:

mvn -f testsuite/integration-arquillian/pom.xml \
      clean install \
      -Pauth-server-wildfly \
      -Dtest=SocialLoginTest \
      -Dbrowser=chrome \
      -Dsocial.config=/path/to/social.properties

Different Browsers

Mozilla Firefox

• Supported version: latest ESR (Extended Support Release)
• Driver download required: no
• Run with: -Dbrowser=firefox; optionally you can specify -Dfirefox_binary=path/to/firefox/binary

Google Chrome

• Supported version: latest stable
• Driver download required: ChromeDriver which corresponds with your version of the browser
• Run with: -Dbrowser=chrome -Dwebdriver.chrome.driver=path/to/chromedriver

Internet Explorer

• Supported version: 11
• Driver download required: Internet Explorer Driver Server; recommended version 2.53.1 32-bit
• Run with: -Dbrowser=internetExplorer -Dwebdriver.ie.driver=path/to/IEDriverServer.exe

Run X.509 tests

To run the X.509 client certificate authentication tests:

mvn -f testsuite/integration-arquillian/pom.xml \
      clean install \
  -Pauth-server-wildfly \
  -Dauth.server.ssl.required \
  -Dbrowser=phantomjs \
  "-Dtest=*.x509.*"

Cluster tests

Cluster tests use 2 backend servers (Keycloak on Wildfly/EAP) and 1 frontend loadbalancer server node. Invalidation tests don't use loadbalancer. The browser usually communicates directly with the backend node1 and after doing some change here (eg. updating user), it verifies that the change is visible on node2 and user is updated here as well.

Failover tests use loadbalancer and they require the setup with the distributed infinispan caches switched to have 2 owners (default value is 1 owner). Otherwise failover won't reliably work.

The setup includes:

• a mod_cluster load balancer on Wildfly
• two clustered nodes of Keycloak server on Wildfly/EAP

Clustering tests require MULTICAST to be enabled on machine's loopback network interface. This can be done by running the following commands under root privileges:

route add -net 224.0.0.0 netmask 240.0.0.0 dev lo
ifconfig lo multicast

Then after build the sources, distribution and setup of clean shared database (replace command according your DB), you can use this command to setup servers:

export DB_HOST=localhost
mvn -f testsuite/integration-arquillian/servers/pom.xml \
-Pauth-server-wildfly,auth-server-cluster,jpa \
-Dsession.cache.owners=2 \
-Djdbc.mvn.groupId=mysql \
-Djdbc.mvn.version=5.1.29 \
-Djdbc.mvn.artifactId=mysql-connector-java \
-Dkeycloak.connectionsJpa.url=jdbc:mysql://$DB_HOST/keycloak \
-Dkeycloak.connectionsJpa.user=keycloak \
-Dkeycloak.connectionsJpa.password=keycloak \
clean install

And then this to run the cluster tests:

mvn -f testsuite/integration-arquillian/tests/base/pom.xml \
-Pauth-server-wildfly,auth-server-cluster \
-Dsession.cache.owners=2 \
-Dbackends.console.output=true \
-Dauth.server.log.check=false \
-Dfrontend.console.output=true \
-Dtest=org.keycloak.testsuite.cluster.**.*Test clean install

Cluster tests with embedded undertow

Run cluster tests from IDE

The test uses Undertow loadbalancer on http://localhost:8180 and two embedded backend Undertow servers with Keycloak on http://localhost:8181 and http://localhost:8182 . You can use any cluster test (eg. AuthenticationSessionFailoverClusterTest) and run from IDE with those system properties (replace with your DB settings):

-Dauth.server.undertow=false -Dauth.server.undertow.cluster=true -Dauth.server.cluster=true 
-Dkeycloak.connectionsJpa.url=jdbc:mysql://localhost/keycloak -Dkeycloak.connectionsJpa.driver=com.mysql.jdbc.Driver 
-Dkeycloak.connectionsJpa.user=keycloak -Dkeycloak.connectionsJpa.password=keycloak -Dkeycloak.connectionsInfinispan.clustered=true -Dresources	 
-Dkeycloak.connectionsInfinispan.sessionsOwners=2 -Dsession.cache.owners=2    

Invalidation tests (subclass of AbstractInvalidationClusterTest) don't need last two properties.

Run cluster environment from IDE

This mode is useful for develop/manual tests of clustering features. You will need to manually run keycloak backend nodes and loadbalancer.

1. Run KeycloakServer server1 with:

   -Dkeycloak.connectionsJpa.url=jdbc:mysql://localhost/keycloak -Dkeycloak.connectionsJpa.driver=com.mysql.jdbc.Driver -Dkeycloak.connectionsJpa.user=keycloak -Dkeycloak.connectionsJpa.password=keycloak -Dkeycloak.connectionsInfinispan.clustered=true -Dkeycloak.connectionsInfinispan.sessionsOwners=2 -Dresources

and argument: -p 8181

2. Run KeycloakServer server2 with same parameters but argument: -p 8182

3. Run loadbalancer (class SimpleUndertowLoadBalancer) without arguments and system properties. Loadbalancer runs on port 8180, so you can access Keycloak on http://localhost:8180/auth

Cross-DC tests

Cross-DC tests use 2 data centers, each with one automatically started and one manually controlled backend servers (currently only Keycloak on Undertow), and 1 frontend loadbalancer server node that sits in front of all servers. The browser usually communicates directly with the frontent node and the test controls where the HTTP requests land by adjusting load balancer configuration (e.g. to direct the traffic to only a single DC).

For an example of a test, see org.keycloak.testsuite.crossdc.ActionTokenCrossDCTest.

The cross DC requires setting a profile specifying used cache server (currently only Infinispan) by specifying cache-server-infinispan profile in maven.

Run Cross-DC Tests from Maven

First compile the Infinispan/JDG test server via the following command:

mvn -Pcache-server-infinispan -f testsuite/integration-arquillian -DskipTests clean install

or

mvn -Pcache-server-jdg -f testsuite/integration-arquillian -DskipTests clean install

Then you can run the tests using the following command (adjust the test specification according to your needs):

mvn -Pcache-server-infinispan -Dtest=*.crossdc.* -pl testsuite/integration-arquillian/tests/base test

or

mvn -Pcache-server-jdg -Dtest=*.crossdc.* -pl testsuite/integration-arquillian/tests/base test

Someone using IntelliJ IDEA, please describe steps for that IDE