[MGNLTEST-277] Webdriver/ui-test setup should be less lazy (in Selenium extension) Created: 24/Jun/22  Updated: 26/Oct/22  Resolved: 05/Oct/22

Status: Closed
Project: Magnolia Test Framework
Component/s: None
Affects Version/s: None
Fix Version/s: 1.4.0

Type: Improvement Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Epic Link: cucumber-and-selenide-support-by-test-fwk

 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.



 Comments   
Comment by Christoph Meier [ 05/Oct/22 ]

Has been tackled with MGNLTEST-286

Generated at Mon Feb 12 07:47:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.