Loading
Fix flaky boards list settings feature specs
What does this MR do and why?
Fix flaky boards list settings feature specs
The list settings examples create two boards, then visited
project_boards_path, which resolves the default board through
BoardsFinder. That finder orders by LOWER(name), and the EE board
factory names boards from a sequence, so board10 sorts ahead of
board9. Whenever a pair straddled a digit-count boundary the
milestone board loaded instead, and the label list every example in
the context depends on was absent. Pinning the board removes the
ambiguity.
The rest of the change drops selectors that cannot express what they
mean. :nth-child(2) counts every sibling rather than every matching
column, so it resolved to whichever list happened to be second.
.gl-drawer-close-button is a gitlab-ui internal class, which the
spec's own comment warned about, so use the drawer's accessible name.
.native hands back a raw Selenium element and so opts out of
Capybara's automatic reload, meaning a re-render between setting the
input and sending Enter raises a stale element reference with no
retry.
References
Screenshots or screen recordings
Not provided
How to set up and validate locally
bundle exec rspec ee/spec/features/boards/boards_spec.rb
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #623133 (closed)