Project

Reverse Dependencies for rspec-core

The projects listed here declare rspec-core as a runtime or development dependency

0.0
The project is in a healthy, maintained state
Provides a rich DSL for RSpec to assert on files, directories, and symlinks, including permissions, content (including JSON), and more. Ideal for testing generators and build scripts.
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
A custom RSpec formatter that suppresses detailed pending test output and shows only the count in the summary
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
Sometimes every example in an RSpec example group fails because of a bug in the before hook. Wouldn't you rather see the error only once, rather than for every single example? Now you can.
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
Tweaks the built-in RSpec formatters to cause failures to be printed immediately when they occur.
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
retry rspec one target `expect` instead of one `secenario` or `it`
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
rspec-rewind provides deterministic retry policies, exception filters, configurable backoff strategies, and flaky test observability for RSpec.
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
Detects RSpec examples that execute no expectations or write unexpected stdout/stderr output.
2021
2022
2023
2024
2025
2026
0.0
Low commit activity in last 3 years
No release in over a year
DSL to make testing side effects clear and explicit.
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
An RSpec profiler that shows you how long specs are spending in `sleep`
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
When you run individual specs, I want to see documentation output, because it shows better which specs fails. But when I run all my specs I want something like progress or Fuubar.
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
Report status and duration of RSpec runs to statsd
2021
2022
2023
2024
2025
2026
0.0
No release in over a year
Fork of rswag-specs. Compatible with any rack framework like Sinatra, Padrino, Hanami, Roda, etc. Simplify API integration testing with a succinct rspec DSL and generate OpenAPI specification files directly from your rspec tests. More about the OpenAPI initiative here: http://spec.openapis.org/
2021
2022
2023
2024
2025
2026
0.0
Low commit activity in last 3 years
There's a lot of open issues
No release in over a year
RSpec DSL which makes is easier and cleaner to write tabular examples.
2021
2022
2023
2024
2025
2026