Update blog/2024/preview-keycloak-test-framework.adoc

Co-authored-by: Šimon Vacek <86605314+vaceksimon@users.noreply.github.com>
Signed-off-by: Lukas Hanusovsky <61745358+lhanusov@users.noreply.github.com>

blog/2024/preview-keycloak-test-framework.adoc

@@ -11,7 +11,7 @@ It would be good to mention a few drawbacks, that stand out when working with th
 
 == Brighter Future?
 
-Keycloak team had started a https://github.com/orgs/keycloak/projects/42[joint effort] between the engineering and quality engineering people to design a new https://github.com/keycloak/keycloak/tree/main/test-framework[test framework] (May 2024). It had been initiated with a prototype to verify, if our thoughts are feasible. The prototype should have been based on the _JUnit5_ testing framework, specifically to implement _JUnit5_ callback classes which extend the default test lifecycle functionality and provide custom inject annotations, like _@KeycloakIntegrationTest_, _@InjectWebDriver_ or _@InjectRealm_.
+Keycloak team had started a https://github.com/orgs/keycloak/projects/42[joint effort] between the engineering and quality engineering people to design a new test framework (May 2024). It had been initiated with a prototype to verify if our thoughts were feasible. The prototype was based on the _JUnit5_ testing framework, specifically to implement _JUnit5_ callback classes which extend the default test lifecycle functionality and provide custom inject annotations, like _@KeycloakIntegrationTest_, _@InjectWebDriver_ or _@InjectRealm_.
 
 For our purpose, we have https://github.com/keycloak/keycloak/blob/main/test-framework/src/main/java/org/keycloak/test/framework/KeycloakIntegrationTestExtension.java[implemented] these three callback classes:
 ----