[MGNLTEST-272] Fix timeout issues while executing PagesSpa*Tests Created: 07/Jun/22  Updated: 13/Jul/22  Resolved: 04/Jul/22

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

Type: Bug Priority: Neutral
Reporter: Rishab Dhar Assignee: Rishab Dhar
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 1h Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLTEST-273 Implemation Sub-task Completed Rishab Dhar  
MGNLTEST-274 Review Sub-task Closed Oanh Thai Hoang  
MGNLTEST-275 PiQA Sub-task Completed  
MGNLTEST-276 QA Sub-task Completed  
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
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: SaaS TPR - SPA Tests
Sprint: DevX 13
Story Points: 5
Team: DeveloperX

 Description   

As part of DEV-1927 scaled external SPA docker setup was introduced, but on executing the tests now in external SPA mode, the tests fail due to likely delays introduced on fetching and rendering content from external SPA because of which the selectors for areas, components fail as a result of timeouts.

Steps to reproduce

  • Simply trigger the build of PR into master or release/6.2
  • You should see the stacktrace and the resulting recording of the failed test.

Notes

Trying our ImplicitWaitTimeout annotation on the tests yields no success either.



 Comments   
Comment by Christopher Zimmermann [ 14/Jun/22 ]

Just wondering if this could be a bug in the SPA libraries? There is this ticket currently being worked on that also relates to timing issues:https://jira.magnolia-cms.com/browse/MGNLFE-208 cc: rsiska 

Comment by Christopher Zimmermann [ 23/Jun/22 ]

That bug is now fixed on npm - the frontend project would just have to use version 1.2.3-beta of react-editor  or whatever flavor. Probably worth a try.

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