A simple CLI to watch file changes and run their matching ruby specs. Works on any ruby projects with no setup.
This release fixes on our CI pipeline and the bundler version set incorrectly in the previous release v1.13.1
Ruby 3.4 will require the observer
gem to be set as an explicit dependency in a Gemfile and will no longer be included in the language: https://bugs.ruby-lang.org/issues/20187
This release adds observer gem as an explicit Retest dependency.
In this release, apparent changes are on the list of possible options:
>
at the end to improve user feedback #192The list looks like this now
We found few tests matching: app/models/valuation/holdings.rb
[0] - test/models/taxation/holdings_test.rb
[1] - test/models/schedule/holdings_test.rb
[2] - test/models/holdings_test.rb
[3] - test/models/performance/holdings_test.rb
[4] - test/lib/csv_report/holdings_test.rb
[5] - none
Which file do you want to use?
Enter the file number now:
>
In minor improvements with no impact
This release adds a few changes
--notify
, retest is now making a sound after asking to select a file when in doubtListen.logger
dependency and available with LISTEN_GEM_DEBUGGING=warn
--verbose
, -v` to see which version of retest we're currently usingThese issues are fixed:
The release improves the identification of test files with test
and spec
prefix or suffix.
The release also updates some dependencies suggested by Dependabot.
Main change:
Since December 2021, Bundler gem now defaults to test_filename.rb
instead of filename_test.rb
in release 2.3.0
bundle gem generated MiniTest file and class now start with 'test' https://github.com/rubygems/rubygems/pull/3893
This release addresses this change by updating what's considered a test file when matching specs.
A change in filename.rb
will now consider these files as possible matches:
filename_test.rb
filename_spec.rb
test_filename.rb
spec_filename.rb
(because why not)Someone suggested to gracefully exit Retest
when pressing ctrl
+ c
instead of showing the ruby trace: #124
This release enables the software to print "Goodbye" after exiting retest.
Some filesystems won't work without polling (VM/Vagrant Shared folders, NFS, Samba, sshfs, etc.). https://github.com/guard/listen#issues--limitations
In this situation we introduce a new flag --polling
to force the polling method on the Listen
gem when using retest
Examples:
$ retest --polling
$ retest --polling --all
$ retest --polling 'bundle exec rubocop <changed>'
The --auto option is run by default, there is no need to make it explicit.
retest -h
# Old behaviour
$ retest --auto
$ retest --auto --all
# New behaviour
$ retest
$ retest --all
This release fixes:
We play another sound when restest starts. Using the same sound of a test passing and retest starting is confusing. The sounds should be distinct otherwise it feels like Retest ran the suite.
A minor change updating a copy to make things a bit clearer.
This release includes: #108 #112
Fixing: #82