Details
-
Improvement
-
Resolution: Duplicate
-
Neutral
-
None
-
None
Description
Context:
We made Webdriver/ui-test setup in the Selenium extension "lazy" some time ago.
Whis was done to ensure webdriver/vncrecorder are set up only when a test is a UI-test.
While our UI tests were only "classic" tests (no cucumber) and all were using either PageObjects or Navigator ...
... the "lazy" setup was handled inĀ Selenium#resolveParameter.
But now - after Selenide support was added to the test-fwk - we can write UI-tests without the need for PageObjects or Navigator ...
This change requires a change in the lazy setup for UI-tests.
Checklists
Acceptance criteria