Bug 1512539
| Summary: | secondary navigation menu has open initial state which breaks testing | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Aleksandar Kostadinov <akostadi> | ||||||||||||
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Yadan Pei <yapei> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 3.7.0 | CC: | akostadi, aos-bugs, jokerman, mmccomas, spadgett, xiaocwan, yanpzhan, yapei | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | 3.8.0 | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2017-11-13 21:08:16 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Attachments: |
|
||||||||||||||
Created attachment 1351564 [details]
timeline 1
Created attachment 1351565 [details]
timeline 2
Created attachment 1351566 [details]
timeline 3
Created attachment 1351579 [details]
Chrome timeline
I'm not able to reproduce. See attached animated gif that has a Chrome timeline of the page loading. Please let us know specifically what the automated tests are doing so we can try the exact steps.
Note that the nav elements are now persistent. As you navigate between pages, they are not removed and re-added to the DOM like before. They do not appear to be open on first page load in my testing, however.
Aleksandar, could you let us know exactly what the tests are doing so we can better reproduce? |
Created attachment 1351563 [details] timeline 0 Description of problem: When a console page is loaded, the initial state of the secondary navigation menu is open. Then it seems some js is kicking in to close it. Automated tests can't know when it becomes closed. So a scenario like: 1. selenium open some URL 2. wait for "Configuration" tab to appear 3. click on configiuration tab It sometimes happens such that secondary navigation is not closed while we try to click configuration tab. Because that tab is under the secondary navigation menu, the click fails in selenium and test is marked as failed. There are no trivial workarounds for this sporadic behavior except adding sleep times. And this will slowdown overall execution significantly. Attaching screenshots that demonstrate how the page has been opening. Version-Release number of selected component (if applicable): v3.7.4 472090f How reproducible: sometimes