Fixing Flaky End-to-End (E2E) Tests in Ruby

Flaky tests are tests that sometimes fail for no obvious reason. They are the plague of many end-to-end (E2E) test suites that automate the browser through tools like Capybara and Selenium.

Tolerating flaky tests for too long can cause your team to lose faith in your E2E test suite and eventually abandon it. But even though flaky tests feel like random events of bad luck, they really are not! By understanding the timing issues of your test scripts, you can stabilize any test suite, even in large legacy applications.

In this episode of Full Stack Hour we will cover the following topics:

• Which patterns are known to cause flaky tests?
• How does Capybara and Selenium synchronize between our test and the browser? What are the limits of the built-in synchronization mechanisms?
• How can we detect and fix timing issues in our tests?
• Stabilizing E2E test suites in legacy projects.

The talk will be held in English.

Code examples will focus on Ruby, but techniques are applicable to all languages.

Dial-in via Browser:
https://us02web.zoom.us/wc/join/85173027072?pwd=azJtenUwbnVtY090SnZ0S2h3RlcwQT09

Dial-in via Client:
Meeting-ID: 851 7302 7072
Code: 379080