Speccloak is a lightweight CLI tool that checks if the lines you've changed in your Git branch are covered by your test suite. It helps you prevent untested changes from creeping into the codebase — effortlessly.
- Compares your current branch with a base branch (e.g.
origin/main
) - Analyzes which lines have changed
- Uses SimpleCov's
.resultset.json
to verify test coverage for those lines - Highlights which changed lines are not covered
- Supports
.speccloak.yml
config file and CLI overrides - Outputs results in
text
orjson
- Code reviewers can skip worrying about if this lengthy PR changes has all of its lines covered by the specs.*
- Private methods are tested through the main method without stubbing them.*
- Developers get instant feedback on whether their changes are adequately tested before merging.*
- Teams can enforce branch coverage as a required CI check, preventing untested code from being merged.*
- Legacy codebases can incrementally improve coverage by focusing only on changed lines, not the entire project.*
- Helps maintain high code quality and confidence during refactoring or large-scale changes.*
- Automates the tedious process of manually checking coverage reports for every pull request.*
gem install speccloak
git clone https://github.com/alpinesarecool/speccloak.git
cd speccloak
gem build speccloak.gemspec
gem install ./speccloak-0.1.0.gem
Create a .speccloak.yml
in your project root:
base: origin/main # The branch to diff against
format: text # text or json
exclude: # Exclude these path from checking the coverage
- db/migrate
- spec/
- config/initializers
You can override these via CLI options as well.
speccloak --help
Usage: speccloak [options]
--base BRANCH Specify the base branch (default: origin/main)
--format FORMAT Output format (text or json)
-h, --help Display help information
speccloak
speccloak --base origin/develop --format json --exclude []
If you have added speccloak
to your Gemfile:
gem 'speccloak'
You can run Speccloak as part of your CI pipeline.
Here’s an example GitHub Actions step:
- name: Install dependencies
run: bundle install --jobs 4 --retry 3
- name: Run Speccloak branch coverage check
run: bundle exec speccloak
Tip:
- Make sure you have simplecov gem and when you run the specs it generates the coverage
- Make sure your test suite runs before Speccloak so that coverage data is generated.
- You can add this step after your
bundle exec rspec
or test step.
Example full workflow:
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: ruby/setup-ruby@v1
with:
ruby-version: '3.3'
bundler-cache: true
- name: Install dependencies
run: bundle install
- name: Run tests
run: bundle exec rspec
- name: Run Speccloak branch coverage check
run: bundle exec speccloak
File: app/models/user.rb
Changed lines: 12, 13
All changed lines are covered!
BRANCH COVERAGE REPORT SUMMARY
----------------------------------------
Total changed lines: 2
Covered changed lines: 2
Coverage percentage: 100%
Uncovered lines by file:
app/services/payment_handler.rb:
Line 42: call_external_api
Coverage check failed: Above lines are not covered by specs.
To run the CLI directly from source:
bundle exec exe/speccloak
After bumping the version in lib/speccloak/version.rb
:
gem build speccloak.gemspec
gem push speccloak-<version>.gem
MIT © Nitin Rajkumar Paruchuri
After checking out the repo, run bin/setup
to install dependencies. Then, run rake spec
to run the tests. You can also 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
, which will create a git tag for the version, push git commits and the created tag, and push the .gem
file to rubygems.org.
Bug reports and pull requests are welcome on GitHub at https://github.com/alpinesarecool/speccloak. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.
The gem is available as open source under the terms of the MIT License.
Everyone interacting in the Speccloak project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.