[MGNLTEST-44] Implicit wait timeout may be inconsistent during test execution Created: 16/Jan/20 Updated: 08/Jul/20 Resolved: 22/Jan/20 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Federico Grilli | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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
|
| Epic Link: | core-TF-features-bugs-improvements |
| Sprint: | now |
| Story Points: | 3 |
| Description |
|
Found out this issue while trying to use the new @ImplicitWaitTimeout in a test with a "long running" action such as publishing a new page. Here's the relevant code app.hitAction("Publish"); assertTrue(app.activationStatusToBe("foobar", PUBLISHED)); Despite an ImplicitWaitTimeout of 60 seconds the assertion (which internally uses webDriver.findElement(locator)) would fail after ~10s. |
| Comments |
| Comment by Federico Grilli [ 16/Jan/20 ] |
|
Issue found while working at |