Remote server lag makes selenium tests fail

Bug #1813670 reported by Nicolas Helgeson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Undecided
Akihiro Motoki

Bug Description

When running selenium tests locally, web elements appear in time for selenium to pick up on them. For example, checking for the green confirmation box when switching between projects. However, if the pop up takes too long, selenium fails. I have also run into issues where a modal will appear, but selenium is unable to find it in the dom. Selenium tests should be made more robust and offer more retries and wait just a little longer when necessary.

Changed in horizon:
assignee: nobody → Nicolas Helgeson (nhelgeson)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/633616

Changed in horizon:
status: New → In Progress
Changed in horizon:
assignee: Nicolas Helgeson (nhelgeson) → Akihiro Motoki (amotoki)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.opendev.org/633616
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=78e382c3a5e84fa838d1ede8c49bab515150a7dd
Submitter: Zuul
Branch: master

commit 78e382c3a5e84fa838d1ede8c49bab515150a7dd
Author: nicolas <email address hidden>
Date: Mon Jan 28 14:45:43 2019 -0800

    Selenium tests fail when response is slow.

    Increased implicit wait on message pop ups.
    Gives time for slow connections to wait for message.

    Find_elements retry. Gives an additional opportuninty
    for elements to be found.

    Additional attempts for _execute gives time for
    elements to move or dissapear when collision is a
    problem.

    Change-Id: I94670628c179f7291162f2c25947673f03106fc2
    Closes-Bug: #1813670

Changed in horizon:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 16.0.0.0b2

This issue was fixed in the openstack/horizon 16.0.0.0b2 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.