Anticipate Timeout-Exceptions on UI tests
(MGNLTEST-208)
|
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Christoph Meier |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | VN-Testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Description |
|
We wrap both Driver and WebElement into VaadinDriverWrapper and VaadinELementWrapper. Find-element methods of the wrappers call vaadinIsDone - waiting until all client-sided async-calls are done. Problem is - it happens that it is never done. E.g. that's the underlying probem of MGNLTEST-198 Aim: Introduce Annotation to skip the vaadinIsDone-calls on class- and/or method-level. |
| Comments |
| Comment by Christoph Meier [ 01/Apr/22 ] |
|
First work is done here - thought it looks like it does not resolve the issue of MGNLTEST-198 |
| Comment by Christoph Meier [ 25/Apr/22 ] |
|
I have a branch which implements such an annotation - and does indeed skip the wrapper. However - this approach apparently doesn't seem to solve the problem of timeouts. Plus we were able to avoid the "vaadin is never done" scenario - which was one of the reason for this ticket. I close this subtask with "won't fix" (or the like) |