b1ebc51f00
Background: * We hook deep into RSpec internals to get very fine grained test selection * These APIs are NOT public. * Hence mutant was always very restrictive in its versioning, to not whitelist a version where these internals are eventually changed. * No such change happened in years. Conclusion: * The past approach of whitelisting rspec version after rspec version is not the correct choice for reducing the mutant maintainership workload. * We'll eat the potential regression over not automatically covering new rspec releases in the 3.x series (yeah, I know potentially last famous words).
22 lines
871 B
Ruby
22 lines
871 B
Ruby
require File.expand_path('../lib/mutant/version', __FILE__)
|
|
|
|
Gem::Specification.new do |gem|
|
|
gem.name = 'mutant-rspec'
|
|
gem.version = Mutant::VERSION.dup
|
|
gem.authors = ['Markus Schirp']
|
|
gem.email = ['mbj@schirp-dso.com']
|
|
gem.description = 'Rspec integration for mutant'
|
|
gem.summary = gem.description
|
|
gem.homepage = 'https://github.com/mbj/mutant'
|
|
gem.license = 'MIT'
|
|
|
|
gem.require_paths = %w[lib]
|
|
gem.files = `git ls-files -- lib/mutant/integration/rspec.rb`.split("\n")
|
|
gem.test_files = `git ls-files -- spec/{integration,unit}/mutant/rspec_spec.rb}`.split("\n")
|
|
gem.extra_rdoc_files = %w[LICENSE]
|
|
|
|
gem.add_runtime_dependency('mutant', "~> #{gem.version}")
|
|
gem.add_runtime_dependency('rspec-core', '>= 3.4.0', '< 4.0.0')
|
|
|
|
gem.add_development_dependency('bundler', '~> 1.3', '>= 1.3.5')
|
|
end
|