8000 Generate random passwords for imported users in forms and webauthn tests by rmartinc · Pull Request #38935 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Generate random passwords for imported users in forms and webauthn tests - #38935

Merged
mposolda merged 1 commit into
keycloak:mainfrom
rmartinc:issue-38812-2
Apr 15, 2025
Merged

mposolda merged 1 commit into
keycloak:mainfrom
rmartinc:issue-38812-2

Conversation

@rmartinc
Copy link
Copy Markdown
Contributor

Closes #38812

Finally to test with chrome the passwords are going to be re-genearted for imported users. The password is saved inside a map that can be retrieved during the tests. There are also helper methods to add new passwords into the map or even change the password of a user in the server and the map. All this setup is done in an abstract class called AbstractChangeImportedUserPasswordsTest that any other test class can extend. Modified all the tests in forms and webauthn to use the new generated passwords instead of fixed passwords and, this way, avoid security popups.

CI configured back to use chrome in the ubuntu box.

@mposolda mposolda left a comment •
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rmartinc To me, it looks good. Thanks for the work!

Regarding the failing tests:

  • external links documentation test can be ignored (it is being already fixed by #38094 )
  • For the UI failures, I am not 100% sure. I did not saw those in my recent PR and in the nightly build. I've tried to re-run the tests. Maybe that helps. If re-run does not help, maybe rebase helps (as there are some UI changes yesterday evening, which might fixed this, but not 100% sure...)

However if even rebase does not help, maybe it is UI themselves failing with the latest chrome. As I am not 100% sure if UI tests are also using the chrome prepared in install-chrome action? If it is the case, we can maybe keep the chrome version in this PR still at 134.0.6998.165 and merge the PR. Then there would need to be follow-up PR, which would fix the UI tests and updates chrome to default . But maybe not needed, we will see if re-run or rebase helps...

@rmartinc
8000 rmartinc commented Apr 15, 2025
Copy link
Copy Markdown
Contributor Author

Rebased! Let's see what happens.

@mposolda mposolda left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rmartinc Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Test failures in CI in Chrome tests

2 participants

0