[MGNLTEST-50] Resolve timing-related failures in new UI tests Created: 17/Sep/19 Updated: 14/Dec/20 Resolved: 23/Sep/19 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Federico Grilli | Assignee: | Unassigned |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Epic Link: | core-TF-features-bugs-improvements | ||||||||
| Sprint: | now | ||||||||
| Description |
|
Some page object self tests in the new UI test framework seem to fail rather frequently, especially on Jenkins, namely info.magnolia.testframework.selftest.ContentAppSelfTest#unselectRowByPath info.magnolia.testframework.selftest.MediaEditorSelfTest#mediaEditorPerformsAction info.magnolia.testframework.selftest.AlertNotificationSelfTest#alertConfirmAndNotification See also https://jenkins.magnolia-cms.com/blue/organizations/jenkins/ce/detail/MGNLCE-166-page-extraction Increasing the wait timeout for some possibly long actions, such as when hitting the "save" or "commit" button in forms or alerts only partially helps. Locally, I observed that sometimes such tests fail the first time but pass the second time around, if one repeats them. Would be nice to have a @RetryOnFailure annotation also for JUnit5. There actually is a native @Repeated one but it doesn't take failures into account. Also tried some 3rd party JUnit extensions as suggested here https://www.swtestacademy.com/junit-5-how-to-repeat-failed-test/ but sadly they didn't work that great. |
| Comments |
| Comment by Federico Grilli [ 23/Sep/19 ] |
|
Closing this as, in the meantime, all issues with failing tests have been solved in |