Skip to content
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

Add automated testing for new Keycloak releases #3

Open
stianst opened this issue Mar 14, 2024 · 2 comments
Open

Add automated testing for new Keycloak releases #3

stianst opened this issue Mar 14, 2024 · 2 comments

Comments

@stianst
Copy link
Contributor

stianst commented Mar 14, 2024

Description

Add continuous testing for the extension that can verify if the extension works as expected with the latest nightly builds of Keycloak, and have automation in terms of testing when a new release of Keycloak is out.

Discussion

No response

Motivation

No response

Details

No response

@stianst
Copy link
Contributor Author

stianst commented Mar 22, 2024

I'm thinking it would be good to have two different types of test:

  • Regular tests - would start KC in embedded mode - kinda like Quarkus @QuarkusTest
  • IT tests - would start KC container with the extension deployed - kinda like Quarkus @QuarkusIntegrationTest

@stianst
Copy link
Contributor Author

stianst commented Mar 22, 2024

Maybe we should either just use Quarkus stuff directly, or do similar things like:

@KeycloakTest
@KeycloakIntegrationTest

Then we could have stuff like:

@KeycloakConfig
@KeycloakRealm

Could take some insipration from what Quarkus has around test profiles.

Inject an admin client:

@KeycloakAdminClient

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant