A CLI tool that monitors file changes and automatically runs corresponding Ruby tests with zero setup required.
Retest is a CLI tool that automatically runs Ruby tests when files change. It monitors your project directory and executes the corresponding test files, eliminating the need to manually run tests during development. The tool requires zero configuration and works with any Ruby project out of the box.
Ruby developers who practice test-driven development or frequently refactor code and want to maintain test coverage without manual intervention. It's particularly useful for developers working on Rails, RSpec, Minitest, or other Ruby testing frameworks.
Developers choose Retest because it requires absolutely no setup—no Gemfile changes, no configuration files—and works instantly with any Ruby project. Its intelligent test detection and customizable commands provide a seamless, automated testing workflow that saves time and reduces context switching.
A trusty CLI companion to monitor file changes and automatically run the corresponding Ruby specs. Ready to assist on any Ruby project, no setup needed!
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Works immediately on any Ruby project without modifying Gemfiles or adding config files, as highlighted in the README's plug-and-play approach.
Automatically runs only relevant tests based on file modifications using Listen or Watchexec, saving time during refactoring and development.
Supports flexible placeholders like <test> and <changed> for tailoring test commands, allowing integration with tools like Rubocop as shown in examples.
Functions seamlessly inside Docker containers, ensuring consistent testing workflows across local and containerized setups without extra setup.
Performance hinges on optional watchers like Watchexec, which must be installed separately and can introduce compatibility or installation overhead.
Only triggers tests on file changes, making it unsuitable for complex test suites with external dependencies or non-file-based events.
Lacks built-in support for parallel test execution or detailed test reporting, focusing solely on automatic triggering rather than comprehensive test management.