From e1a4f7f485679a8b8ac034bb0ef858418a4c7d0e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Barto=C5=A1?= Date: Tue, 31 Aug 2021 11:45:19 +0200 Subject: [PATCH] KEYCLOAK-19147 Update Test development section for PRs --- docs/tests-development.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/tests-development.md b/docs/tests-development.md index 4427c02be8..c350132e17 100644 --- a/docs/tests-development.md +++ b/docs/tests-development.md @@ -22,3 +22,8 @@ you need and use that as a basis. All tests don't have to be fully black box testing as the testsuite deploys a special feature to the Keycloak server that allows running code within the server. This allows writing tests that can execute functions not exposed through APIs as well as access data that is not exposed. For an example on how to do this look at org.keycloak.testsuite.runonserver.RunOnServerTest. + +As assertion method use `org.hamcrest.MatcherAssert.assertThat` where possible with a suitable matcher included +in the `org.hamcrest.Matchers.*` package. +It provides much better readability of test failures messages. +Please avoid as much to use set of assertions from `org.junit.Assert.*` package.