[MGNLTEST-139] page objects tends to fail initialization on PublicationWorkflowFunctionalTests#setUp Created: 14/Jan/21  Updated: 18/Jun/21  Resolved: 04/Jun/21

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

Type: Bug Priority: Trivial
Reporter: Adam Siska Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: shaky-test
Remaining Estimate: Not Specified
Time Spent: 1d 3h
Original Estimate: Not Specified

Attachments: PNG File image-2021-01-18-07-54-07-444.png    
Issue Links:
Relates
relates to MGNLTEST-160 Fix shaky Login / provide AdminCentra... Closed
relation
is related to 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 2
Story Points: 5

 Description   

Since MGNLEE-168 there is shakines in passing functional tests here:
https://git.magnolia-cms.com/projects/PLATFORM/repos/dx-core/browse/integration-tests/tests/src/test/java/info/magnolia/functionaltests/PublicationWorkflowFunctionalTests.java#62

Stacktrace org.openqa.selenium.StaleElementReferenceException: 
stale element reference: element is not attached to the page document
  (Session info: chrome=88.0.4324.96)
For documentation on this error, please visit: https://www.seleniumhq.org/exceptions/stale_element_reference.html
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 'ip-172-30-100-76', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-1052-aws', java.version: '1.8.0_152'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 88.0.4324.96, chrome: {chromedriverVersion: 88.0.4324.96 (68dba2d8a0b14..., userDataDir: /tmp/.com.google.Chrome.kouzz4}, goog:chromeOptions: {debuggerAddress: localhost:40377}, javascriptEnabled: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX, proxy: Proxy(), setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true, webdriver.remote.sessionid: 96d5b97aaefdde0a5cebe5e3d5d...}
Session ID: 96d5b97aaefdde0a5cebe5e3d5ddd5a6
	at info.magnolia.functionaltests.PublicationWorkflowFunctionalTests.setUp(PublicationWorkflowFunctionalTests.java:62)

Notes:

 

  • in this the case above, failed line is first use of findBar() after login and most often last image of the run is login dialog (see image attached)
  • fix related TODOs in info.magnolia.functionaltests.PublicationWorkflowFunctionalTests

To reproduce:

    @Test
    void loginLogin(PageObjects expect){
        expect.loginPage().login(Personas.ARMIN);
        expect.loginPage().login(Personas.ERIC);
    }

Note that the 2nd expect.loginPage().login should logout first. The code is valid to swap the user.
But it fails.



 Comments   
Comment by Christoph Meier [ 01/Mar/21 ]

Doesn't seem to be a blocker anymore.

We fix first MGNLTEST-142 and see again.

Comment by Christoph Meier [ 01/Mar/21 ]

Most recent observed failures happen on 
expect.findBar().openApp("Pages")
PublicationWorkflowFunctionalTests#setUp L62

Comment by Christoph Meier [ 04/Jun/21 ]

MGNLTEST-160 was describing the very same issue, and MGNLTEST-160 has been rephrased recently, hence I close this one as obsolete.

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