[MGNLTEST-95] ContentApp fails when directly opening detail sub-app Created: 16/Sep/20 Updated: 21/Sep/20 Resolved: 21/Sep/20 |
|
| Status: | Closed |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.2 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Michael Duerig | Assignee: | Michael Duerig |
| 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
|
| Sprint: | TE 11 |
| Story Points: | 2 |
| Description |
|
The ContentApp page object fails when instantiated with the browser sub-app not visible (i.e. a detail sub-app visible instead). This can be e.g. experienced when navigating to the resources app from the configuration app via contentApp.hitAction("Show in Resource app"). This causes the isNewGrid call in the ContentApp constructor to fail: org.openqa.selenium.NoSuchElementException:
no such element: Unable to locate element: {"method":"xpath","selector":"(//div[contains(@class, 'browser')]//table)[1]"}
(Session info: chrome=85.0.4183.83)
For documentation on this error, please visit: https://www.seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 'ip-172-30-100-12', 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: 85.0.4183.83, chrome: {chromedriverVersion: 85.0.4183.83 (94abc2237ae0c..., userDataDir: /tmp/.com.google.Chrome.KqjxTH}, goog:chromeOptions: {debuggerAddress: localhost:44467}, 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:virtualAuthenticators: true, webdriver.remote.sessionid: 29d365a2b4579a5294d4701a906...}
Session ID: 29d365a2b4579a5294d4701a906695c5
*** Element info: {Using=xpath, value=(//div[contains(@class, 'browser')]//table)[1]}
at info.magnolia.addon.uitest.EcommerceUITest.showConfigurationInResourceApp(EcommerceUITest.java:99)
A possible fix could defer resolving the grid web element until actually needed. |