Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix flaky tests #1877

Merged
merged 1 commit into from
Sep 9, 2024
Merged

Fix flaky tests #1877

merged 1 commit into from
Sep 9, 2024

Conversation

corylown
Copy link
Contributor

@corylown corylown commented Sep 4, 2024

No description provided.

@corylown corylown force-pushed the flaky-tests branch 2 times, most recently from 2f0cf81 to d050771 Compare September 5, 2024 13:03
@corylown corylown changed the title Reset Capybara session Fix flaky tests Sep 5, 2024
@corylown corylown marked this pull request as ready for review September 9, 2024 12:21
Copy link
Contributor

@jcoyne jcoyne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes seem good, but it would be helpful to understand this a little better. Where was this solution found? What is going on here to make them flaky?

@corylown
Copy link
Contributor Author

corylown commented Sep 9, 2024

When the test that checks "dismiss and don't show again" runs first the other tests fail because the session where "don't show again" was set is still in effect. I tried a bunch of different ways to deal with this based on reviewing methods available in the Capybara driver (https://github.com/teamcapybara/capybara/blob/master/lib/capybara/selenium/driver.rb) and quitting the driver is the only one that worked reliably.

@corylown corylown merged commit e85d017 into main Sep 9, 2024
2 checks passed
@corylown corylown deleted the flaky-tests branch September 9, 2024 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants