Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1512539 - secondary navigation menu has open initial state which breaks testing
Summary: secondary navigation menu has open initial state which breaks testing
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.8.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-13 13:11 UTC by Aleksandar Kostadinov
Modified: 2017-11-13 21:08 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-13 21:08:16 UTC


Attachments (Terms of Use)
timeline 0 (deleted)
2017-11-13 13:11 UTC, Aleksandar Kostadinov
no flags Details
timeline 1 (deleted)
2017-11-13 13:11 UTC, Aleksandar Kostadinov
no flags Details
timeline 2 (deleted)
2017-11-13 13:12 UTC, Aleksandar Kostadinov
no flags Details
timeline 3 (deleted)
2017-11-13 13:12 UTC, Aleksandar Kostadinov
no flags Details
Chrome timeline (deleted)
2017-11-13 14:13 UTC, Samuel Padgett
no flags Details

Description Aleksandar Kostadinov 2017-11-13 13:11:19 UTC
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

Comment 1 Aleksandar Kostadinov 2017-11-13 13:11:54 UTC
Created attachment 1351564 [details]
timeline 1

Comment 2 Aleksandar Kostadinov 2017-11-13 13:12:24 UTC
Created attachment 1351565 [details]
timeline 2

Comment 3 Aleksandar Kostadinov 2017-11-13 13:12:50 UTC
Created attachment 1351566 [details]
timeline 3

Comment 4 Samuel Padgett 2017-11-13 14:13:41 UTC
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.

Comment 5 Samuel Padgett 2017-11-13 14:15:28 UTC
Aleksandar, could you let us know exactly what the tests are doing so we can better reproduce?


Note You need to log in before you can comment on or make changes to this bug.