5 Matching Annotations
- Jun 2021
That’s not the only way of writing end-to-end tests in Rails. For example, you can use Cypress JS framework and IDE. The only reason stopping me from trying this approach is the lack of multiple sessions support, which is required for testing real-time applications (i.e., those with AnyCable 😉).
This is why for a recent Angular+Rails project we chose to use a testing stack from the backend technology’s ecosystem for e2e testing.
There are times to stretch individually and as a team, but there are also times to take advantage of what you already know.
This meant that we owned both sides of the product implementation. For unit testing on the frontend, we stayed with Angular’s suggestion of Jasmine. For unit testing on the backend, we went with rspec-rails. These worked well since unit tests don’t need to cross technology boundaries.
We used testing tools that were in the same ecosystem as our backend technology stack for primrily three reasons: We owned both ends of the stack Team experience Interacting with the database
- officially recommended
- determining if something is an appropriate application / best tool for the job
- software stack: choosing
- good advice
- end-to-end testing
- key point
- using disparate technologies in a single project
- explaining why
- testing: stack
- testing: unit tests
- people stick to what they know
- how to choose a dependency/library/framework
- software stack: choosing: factors: familiarity/experience
- testing: stack: choosing
- official preferred convention / way to do something
- testing: end-to-end
- answer the "why?"