[MGNLTEST-222] Try out Selenide Created: 22/Apr/22 Updated: 20/Jun/22 Resolved: 20/Jun/22 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | foundation_team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Description |
|
Selenide claims to solve problems like StaleElementReferenceException, time-outs, etc. (see https://selenide.org/documentation/selenide-vs-selenium.html) Selenide is already used for some SaaS UI-tests (ask Jorge for detail). Try it out in the context of the test-fwk. |
| Comments |
| Comment by Christoph Meier [ 20/Jun/22 ] |
|
Will be tackled by |