Repository navigation
Replies: 2 comments 3 replies
|
Is it planned, that it will be possible to exchange selenium with Playwright ? Im happy to help on that. |
|
We plan to stick with Selenium, but if you want to use Playwright that can be done as a custom extension. The test framework is built to allow creating extensions, and the UI/Selenium is actually an extension already and not included in the core of the test framework. Not sure if Playwright has a similar concept to injecting things into pages? Maybe the pages could be reused as that would probably be the biggest effort of switching between Selenium and Playwright. Could you maybe add some reasons why you'd like to use Playwright instead of Selenium? |
|
I had the following problems with my Mac with arm64:
|
|
I've got the opposite problem with Playwright on Fedora Ideally we would not expose Selenium/WebDriver or Playwright at all, but put it all behind a facade so we can easily switch between the two. That could actually be feasible to do, as we are already not using WebDriver directly in many tests, but rather through facades like @page and PageUtils, etc. |
|
Since it's been 3 months without any specific comment, closing as resolved. |
Uh oh!
There was an error while loading. Please reload this page.
Dear Keycloak community,
Starting from the 26.6.0 release, the new Test Framework is under a full support.
This is a follow-up on the discussion introducing Test Framework as a tech-preview.
What to expect?
Test Framework Guides
Migrating Tests Guide
New features:
This discussion targets Keycloak developers and also Keycloak extension developers, because the framework will enable the feature to install custom providers on the fly.
Thank you for a feedback!
Keycloak team
All reactions