Transient error in spec/features/issues/filtered_search/filter_issues_weight_spec.rb
As seen in,
- https://gitlab.com/gitlab-org/gitlab-ee/builds/18784705
- https://gitlab.com/gitlab-org/gitlab-ee/builds/18786078
Failures:
1) Filter issues weight weight with other filters filters issues by searched weight, author, assignee, label, milestone and text
Failure/Error: filtered_search.send_keys(:enter)
Capybara::Poltergeist::MouseEventFailed:
Firing a click at co-ordinates [1155.5, 421] failed. Poltergeist detected another element with CSS selector 'html body div.page-with-sidebar div.content-wrapper.page-with-layout-nav.page-with-sub-nav div div#content-body.content div.container-fluid.container-limited div.issues-filters div.filtered-search-block.issues-details-filters.row-content-block.second-block form.filter-form.js-filter-form div.issues-other-filters.filtered-search-wrapper div.filtered-search-box.focus button.clear-search i.fa.fa-times' at this position. It may be overlapping the element you are trying to interact with. If you don't care about overlapping elements, try using node.trigger('click').
# ./spec/support/filtered_search_helpers.rb:17:in `input_filtered_search'
# ./spec/features/issues/filtered_search/filter_issues_weight_spec.rb:90:in `block (3 levels) in <top (required)>'
# ./spec/spec_helper.rb:86:in `block (2 levels) in <top (required)>'
# ------------------
# --- Caused by: ---
# Capybara::Poltergeist::BrowserError:
# There was an error inside the PhantomJS portion of Poltergeist. If this is the error returned, and not the cause of a more detailed error response, this is probably a bug, so please report it.
#
# Poltergeist.MouseEventFailed: click
# html body div.page-with-sidebar div.content-wrapper.page-with-layout-nav.page-with-sub-nav div div#content-body.content div.container-fluid.container-limited div.issues-filters div.filtered-search-block.issues-details-filters.row-content-block.second-block form.filter-form.js-filter-form div.issues-other-filters.filtered-search-wrapper div.filtered-search-box.focus button.clear-search i.fa.fa-times
# {"x"=>1155.5, "y"=>421}
# ./spec/support/filtered_search_helpers.rb:17:in `input_filtered_search'
Reasoning
I think this happens because of the author
and assignee
tokens where we swap out the username for an avatar and name
Failing screenshot |
Passing screenshot (locally) |
---|---|
When the test fails, it tries to click on the input, .filtered-search
, but the avatars load in and it accidentally clicks a token instead. I marked the spot, the test tried to click 1155.5, 421
which missed
Edited by username-removed-892863