RSpec vs Jasmine

Free and open source

Free and open source

Free and open source. You pay in engineering time and CI minutes.

Free and open source. You pay in engineering time and CI minutes.

Everything, self-hosted

Everything, self-hosted

Widely used

RSpec Team · since 2005

Established

OSS community · since 2010

• The output reads as documentation of intended behaviour.
• Shared examples and contexts keep large Rails suites organised.
• Deep integration with the Rails ecosystem — Capybara, FactoryBot, VCR.

• Self-contained: spies, clocks and matchers with no extra packages.
• Runs directly in a browser without bundling.
• Extremely stable API — old suites keep working.

• Deeply nested contexts with let and before hooks become very hard to follow.
• The DSL is a language of its own to learn.
• Rails suites tend towards slowness; expect to invest in parallelisation.

• Feels dated; snapshot testing and modern mocking are absent or bolted on.
• Momentum has moved to Jest and Vitest, including within the Angular ecosystem.
• Weaker TypeScript ergonomics than newer runners.

Ruby and Rails applications.

Existing Angular codebases and browser-native test setups.