Enables to click-open RSpec failure backtrace lines

For example: collection.should all_be > 0 will specify that each element of the collection should be greater than zero. Each element of the collection that fails the test will be reported in the error message.

Queue-based parallel test runner for rspec

Designed for CI systems which only outputs row-by-row, this formatter displays current progress in CI friendly way.

A datadog reporter wrapped in an rspec formatter; reports rspec results as datadog events

RSpec extension for distributed running of specs from a queue.

RSpec::Endpoint provides the `endpoint` method as a helper to test HTTP requests. It parses and replaces the description with the informed params.

Modifies RSpec's description generator to produce more natural-sounding English.

Enhanced JSON formatter for RSpec

RSpec matcher to check enqueueing of Sidekiq jobs

A drop-in replacement for RSpec's built-in JSON formatter that adds structured test failure data, making it easy to programmatically analyze test results.

RSpec formater that produces output easily consumable by automated tools

rspec built-in documentation formatter for travis-ci

A collection of useful RSpec 3 formatters

This is a formatter for RSpec 3 that takes advantage of features in WebKit to make the output from running specs in Textmate more fun/useful.

Provides "it_exposes" and "describe_exposure" methods to test Grape Entities

An RSpec plugin to simplify integration tests for GraphQL

A plugin to RSpec and YARD that allows you to define illustrative objects in your examples that will be forwarded to the output formatter. The results can be imported into YARD, which makes your generated specs and documentation more readable, illustrative, and explanatory.

An interactive console for running specs.

redefines is_expected as expect{ subject }