c580c88c93
Adding two feature toggles for new code paths to store online sessions in the existing offline sessions table. Separate the code which is due to be changed in the next iteration in new classes/providers which used instead of the old one. Closes #27976 Signed-off-by: Alexander Schwartz <aschwart@redhat.com> Signed-off-by: Michal Hajas <mhajas@redhat.com> Co-authored-by: Michal Hajas <mhajas@redhat.com> |
||
|---|---|---|
| .. | ||
| src | ||
| pom.xml | ||
| README.md | ||
| test-all-profiles.sh | ||
Model testsuite
Model testsuite runs tests on raw KeycloakSessionFactory which is
initialized only with those providers that are explicitly enabled
in a used profile via keycloak.model.parameters system property.
This allows writing tests and running those in different configurations quickly.
The valid parameters are names of classes in org.keycloak.testsuite.model.parameters
package, and it is possible to combine those by providing multiple class names
separated by comma.
To simplify matters, common combinations of parameters are defined as maven profiles.
Test coverage
To see test coverage via jacoco, set jacoco.skip property to false, e.g.:
mvn test -Pjpa -Dtest=ClientModelTest -Djacoco.skip=false
Then you can generate the coverage report by using the following command:
mvn org.jacoco:jacoco-maven-plugin:0.8.7:report \
-Djacoco.skip=false -Djacoco.dataFile=target/jacoco.exec
The test coverage report is then available from target/site/jacoco/index.html file.
Profiling
If you have Async Profiler
installed, you can generate flame graphs of the test run for profiling purposes.
To do so, you set libasyncProfilerPath system property to the location of the
async profiler library:
mvn test -Pjpa -Dtest=ClientModelTest \
-DlibasyncProfilerPath=/usr/local/async-profiler/build/libasyncProfiler.so
The results are available in the target/profile.html file.