cypress-rails VS cypress-pipe

We use Cypress alongside cypress-rails and Cypress Testing Library.

To piggyback: This would be a type of browser test, so you would want to use something like Cypress (https://github.com/testdouble/cypress-rails) or Capybara (https://github.com/teamcapybara/capybara). RSpec has a good integration with Capybara. Cypress is JS-based so it will require some additional config.

Now a very good news : integrating Cypress to Rails is really simple, because there's already a gem for that. Thanks to the amazing work of the teamdouble team. Their corresponding GitHub repository is here.

Some of the links mentioned in the stream: Forem end-to-end docs Cypress documentation Making your UI tests resilient to change by Kent C. Dodds Forem’s use of Cypress in GitHub Cypress Rails Test Automation University

There's already a tool that perfectly handles this kind of test : Cypress. Why not a gem based on Cypress, that would replace entirely the default system tests stack ? So far, I am very happy with this gem : https://github.com/testdouble/cypress-rails/

We've been working around this with a variety of solutions, including using cypress-pipe which lets us retry a click until a certain condition is met. For example, in the case of the feed preview cards we can do:

But if we want to build an application starting from Redux, and focus on developing tests for the store we can use the cypress-pipe package, which helps Cypress wait to test the store when it's actually updated.