retest | Ruby Ecosystem Directory

retest - Listen to .rb file changes only + Handle new and deleted files

Published by AlexB52 over 3 years ago

This release introduces two changes:

Restrict changes to Ruby files only

Retest now only listens to ruby files is found. Retest feels faster too as we removed the massive Regex used to parse which files to listen to. It is now simpler and snappier.

This becomes the default until a better way to restrict unnecessary files from being watched is found.

Handle new and deleted files

Retest now listens to new and deleted file changes and behave accordingly without having to stop and stage your changes through git.

retest - Flags and Help

Published by AlexB52 almost 4 years ago

You can now print usage with retest --help
You can now use flags to tell retest which standard ruby test command to use
Update README documentation

Shortcut Flags

flags	shortcut command
retest --rake	`bundle exec rake test TEST=<test>`
retest --rake --all	`bundle exec rake test`
retest --rspec	`bundle exec rspec <test>`
retest --rspec --all	`bundle exec rspec`
retest --rails	`bundle exec rails test <test>`
retest --rails --all	`bundle exec rails test`
retest --ruby	`bundle exec ruby <test>`

retest - Support for Ruby 2.4

Published by AlexB52 almost 4 years ago

retest is now usable with Ruby 2.4 projects.
We also improved our CI GitHub actions and added some feature test

retest - Improve Spec Matching Logic

Published by AlexB52 almost 4 years ago

Description

This release improves the spec matching logic to handle more gracefully Hanami projects. No change in the behaviour except you now receive fewer notifications about which test file to run when there are multiple possible tests for a file change.

Issues Fixed

retest - Ignore Untracked File Changes

Published by AlexB52 almost 4 years ago

Description

Retest checks whether git is installed and ignores files in the .gitignore file. This ignores changes you would not normally commit like .byebug_history or sqlite databases files. If you happen to have a file that keeps being updated once you run a test, another test run would get triggered, creating an infinite loop of tests runs.