Test Changes

Test files that have changed since a given commit.

Requirements

• Git

Installation

Add this line to your application's Gemfile:

gem 'test_changes', require: false

And then execute:

$ bundle

Or install it yourself as:

$ gem install test_changes

Configuration

Add a .test_changes.yaml configuration file to your repo. Example:

---
test_tool_command: rspec

finding_patterns:
  ^lib/(.+)\.rb: spec/\1_spec.rb
  ^spec/(.+)_spec.rb: spec/\1_spec.rb

verbose: true

The options

• test_tool_command - The command for running the tests. Example: rspec, zeus rspec.

• finding_patterns - If the name of a changed file matches the regular expression, test_changes will test the file's matching tests. Can accept an array of tests:

  finding_patterns:
    ^lib/test_changes\.rb:
    - spec/test_changes_spec.rb
    - spec/test_changes/client_spec.rb

• verbose - Set the verbose level of output.

Usage

test_changes [test_tool_arguments] [commit]

• test_tool_arguments - Arguments that can be passed to the test tool.

• commit - Test change from this commit. Defaults to HEAD.

Examples:

test_changes
test_changes master
test_changes --format=documentation HEAD^

Known to work on

• Ruby 2.0.0
• Git 2.3.5

Development

After checking out the repo, run bin/setup to install dependencies. Then, run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release to create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Contributing

1. Fork it ( https://github.com/gsmendoza/test_changes/fork )
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request