libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases Packages Activity Actions

KEYCLOAK-14945 Improve the instructions for running the tests

Browse source
This commit is contained in:
mposolda 2020-08-18 17:12:33 +02:00 committed by Marek Posolda
parent bd48d7914d
commit 95d4feedfd
3 changed files with 39 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/building.md
View file

@ -13,13 +13,13 @@ First clone the Keycloak repository:
To build Keycloak run:
mvn install
mvn clean install
This will build all modules and run the testsuite.
To build the ZIP distribution run:
mvn install -Pdistribution
mvn clean install -Pdistribution
Once completed you will find distribution archives in `distribution`.

5
docs/tests.md
View file

@ -1,6 +1,11 @@
Executing tests
===============
Running the tests
-----------------
It is recommended to take a look at [../testsuite/integration-arquillian/HOW-TO-RUN.md](../testsuite/integration-arquillian/HOW-TO-RUN.md).
Browser
-------

32
testsuite/integration-arquillian/HOW-TO-RUN.md
View file

@ -11,6 +11,38 @@ It's recommended to build the workspace including distribution.
cd distribution
mvn clean install
### Running tests in the development mode (Keycloak on embedded undertow)
After build sources and distribution, it is possible to run the base testsuite
mvn -f testsuite/integration-arquillian/pom.xml clean install
Running single test can be achieved for example like this
mvn -f testsuite/integration-arquillian/pom.xml clean install -Dtest=LoginTest
By default, the development setup is used with the Keycloak server deployed on
embedded undertow server. That setup doesn't even require to build the distribution or re-build
the distribution after doing changes in the code.
For example when you do some fix in some class in the `services` module, you can re-build just that module
mvn -f services/pom.xml clean install
And then re-run the LoginTest (or any other test you wish) and the changes should be applied when running the tests.
If you use Intellij Idea, you don't even need to re-build anything with the maven. After doing any
change in the codebase, the change is immediately effective when running the test with Junit runner.
### Running tests in the production mode (Keycloak on Wildfly)
For the "production" testing, it is possible to run the Keycloak server deployed on real Wildfly server.
This can be achieved by add the `auth-server-wildfly` profile when running the testsuite.
mvn -f testsuite/integration-arquillian/pom.xml -Pauth-server-wildfly clean install
Unlike the "development" setup described above, this requires re-build the whole distribution
after doing any change in the code.
## Debugging - tips & tricks