view_component VS cypress-rails

When searching for examples of table components built with the ViewComponent gem, I was surprised to find none. After some inquiries, I came across examples that worked like this:

View components offer two primary ways to interact with the component: passing arguments to the initializer and using slots:

For example, splitting out views into partials? Or the new ViewComponent feature that's becoming quite popular - https://viewcomponent.org/

I used to do "pure ruby" approach to that -- but basically wound up realizing I was re-inventing github's view_component. Their design goals were similar enough to what I was trying to do, that it made more sense just to use that, rather than try to re-invent it myself.

ViewComponent

The linked one is my Rails implementation, written for ViewComponent. The official version uses Nunjucks.

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/