[MGNLTEST-128] Investigate intermittent failures regarding hit action Created: 08/Dec/20  Updated: 05/Jan/21  Resolved: 05/Jan/21

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

Type: Bug Priority: Neutral
Reporter: Šimon Demočko Assignee: Adam Siska
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLUI-6242 Scroll to selected item does not work... Closed
dependency
is depended upon by MGNLEE-628 Implement int. tests publication work... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Fn tests spike 1
Sprint: UI FW 17, UI FW 19
Story Points: 5

 Description   

There was a comment in ActionBar PO which still seems to be relevant:

 // Make sure Vaadin has completed its job as part of whatever code is preceding the call to hitAction(..).
 // Chaining hitAction(..) itself often results in failures, due to Vaadin client-server communication
 // being still active (and thus the DOM not yet ready) as a result of the preceding action execution.

https://git.magnolia-cms.com/projects/PLATFORM/repos/test-framework/commits/907726a6f2999232467c564824708c1dfde13cf0

As latest random failures in CE builds showed this could be intermittent, but chaining hitActions could fail predictably like here in Tasks app:
https://git.magnolia-cms.com/projects/PLATFORM/repos/dx-core/pull-requests/130/overview

So far investigation:

  • element in ActionBar#hitAction method is found and clicked, checked by javascript:
    ((VaadinWebDriverWrapper) driver).executeScript("var ele = arguments[0];ele.addEventListener('click', function() {ele.setAttribute('automationTrack','true');});", action);
    ...
    -> action.getAttribute("automationTrack")
  • situation is the same with:
    action.sendKeys(Keys.ENTER);
    

    or

    ((VaadinWebDriverWrapper) driver).executeScript("arguments[0].click();", action);
    
  • Thread.sleep(5000) at the bottom of this method don't help (but actually might help if used at the test level between hitAction invocations .. weird?)

 



 Comments   
Comment by Christoph Meier [ 16/Dec/20 ]

We have now some hints that MGNLUI-6242 or MGNLUI-6398 could be the culprit for the problems when trying to hot actions. 

Comment by Adam Siska [ 17/Dec/20 ]

This is apparently true as CE is more stable after revert.. Anyway there are still problems when hitting actions in Tasks (and Notification) apps which blocks MGNLEE-628.

Comment by Simon Lutz [ 05/Jan/21 ]

This ^^ problem will be investigated as part of MGNLEE-628.

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