-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Switch testsuite to test with keycloak v2 login theme #30319
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
Switch testsuite to test with keycloak v2 login theme #30319
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.adapter.servlet.SAMLServletAdapterTest#multiTenant1SamlTest
|
f27f246
to
082f0d2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.broker.OidcClaimToUserSessionNoteMapperTest#claimIsPropagatedOnAllLoginsWhenNameMatchesAndSyncModeIsForce
org.keycloak.testsuite.adapter.servlet.SAMLServletAdapterTest#multiTenant1SamlTest
|
173151e
to
6bee030
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.broker.OidcClaimToUserSessionNoteMapperTest#claimIsPropagatedOnFirstLoginOnlyWhenNameMatchesAndSyncModeIsImport
org.keycloak.testsuite.adapter.servlet.SAMLServletAdapterTest#multiTenant1SamlTest
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.adapter.servlet.SAMLServletAdapterTest#multiTenant1SamlTest
|
9e7a645
to
2d55a1f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.adapter.servlet.SAMLServletAdapterTest#multiTenant1SamlTest
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.broker.OidcClaimToUserSessionNoteMapperTest#claimIsPropagatedOnAllLoginsWhenNameMatchesAndSyncModeIsForce
org.keycloak.testsuite.adapter.servlet.SAMLServletAdapterTest#multiTenant1SamlTest
|
2d55a1f
to
718c817
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.adapter.servlet.SAMLServletAdapterTest#multiTenant1SamlTest
|
718c817
to
dea8f2c
Compare
c911eaf
to
62103be
Compare
49ace1f
to
36d9e32
Compare
This PR is being split into #31402 and the testsuite and GHA changes which will be present here. |
36d9e32
to
259831b
Compare
The fixes (mostly selectors) are needed for tests. In the future, to switch the keycloak.v2 to the default theme, do the following: - Update `ThemeSelectorProvider`: Uncomment relevant lines - Update `testsuite/integration-arquillian/tests/pom.xml`: Revert the change in `<login.theme.default>` property - Update `ThemeSelectorTest` per comment Signed-off-by: Hynek Mlnarik <hmlnarik@redhat.com>
259831b
to
04041fa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to merge this to make progress on Login V2. It changes most of the tests to use Login V2. It only affects how tests are run.
We plan to follow up with a PR that will fully test both Login V1 and Login V2 in the nightly build.
Meanwhile, Login V1 is still tested with FIPS tests and Docker tests, which provides us a nice sanity check on Login V1.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes as such LGTM, nice work @hmlnarik with resolving the issue with htmlunit!
My only concern is that we'll be now testing with a different theme that we ship as the default. I understand it's only temporary which is ok. But I wonder if we'll be able to make v2 the default before the next major release, i.e. Keycloak 26, so that we'd test the default.
@vmuzikar Regardless of which login theme is the default, we need to keep both around for awhile. Login V2 needs to be fully vetted in the community before we make it the default for new realms. However, V1 is pretty stable and should require less regression testing. So we want to start testing against V2 as soon as possible because that's where the new development is happening. For performance reasons, we don't want to run the tests against both versions each time a PR is submitted. But we do plan to run both in the nightly build. |
@ssilvert Ok, makes sense. Thanks for clarifying. |
The fixes (mostly selectors) needed for tests.
In the future, to switch the default login theme to
keycloak.v2
, do the following:ThemeSelectorProvider
: Uncomment the relevant linestestsuite/integration-arquillian/tests/pom.xml
: Revert the change in<login.theme.default>
propertyThemeSelectorTest
per commentUncaughtErrorPageTest
per commentWith the prior removal of alpine.js, htmlunit is used again, and the workflow run times are similar to those with original
keycloak
login themeFixes: #29009