-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] Add integration tests to detect breaking changes with new keycloak versions #49
Comments
We could use https://github.com/dasniko/testcontainers-keycloak for this. The real stopper now is a way to test FranceConnect. We could use the test env but this requires to use fixed url for the integration test (and a way to override dns resolution). |
FranceConnect and AgentConnect source here https://github.com/france-connect/sources. Maybe we can use it for integration test. |
@micedre Is it possible to configure a static |
FC+ or AC disallow the use of localhost as authorized redirect_uri. For local tests, they recommend to use a complete domain ( |
Ok, is |
I'll ask, but I don't think it will be accepted. That said, generating a certificate would be hard? |
It can be painful but it's possible ^^ |
Is your feature request related to a problem? Please describe.
We don't check if the plugin is compatible with new keycloak versions
Describe the solution you'd like
Add some integration tests (plugin is deployed, FC theme works, plugin configuration is ok, ...) using Keycloak TestContainers dependency (it starts a Keycloak container only for testing)
Retrieve Keycloak existing versions (using Docker Hub Api: https://hub.docker.com/v2/repositories/jboss/keycloak/tags/?page_size=100)
Execute tests foreach Keycloak Docker Image (from 9.0.2 to latest)
Trigger Github actions workflow every week
The text was updated successfully, but these errors were encountered: