free_mutant/spec/unit/mutant_spec.rb

# frozen_string_literal: true

RSpec.describe Mutant do
  let(:object) { described_class }

  describe '.ci?' do
    subject { object.ci? }

    let(:value) { instance_double(Object, 'value') }

    before do
      expect(ENV).to receive(:key?).with('CI').and_return(value)
    end

    it { should be(value) }
  end
end
Change required Ruby version to >=2.3 * This commit does every 2.3 change required to get the build pass * None of the changes can be extracted, without changing the build setup 2018-09-12 14:21:24 +00:00			`# frozen_string_literal: true`
Upgrade parser dependency 2018-09-12 13:15:43 +00:00
Use RSpec as receiver for rspec DSL methods * I dislike the global infection RSpec does. This commit is a first step to get a rid of it. * Also remove the need for `require 'spec_helper` in each spec file with adjusting `.rspec`. 2014-08-10 21:04:05 +00:00			`RSpec.describe Mutant do`
Add minimal specs for Mutant.zombify 2014-07-06 02:23:11 +00:00			`let(:object) { described_class }`

Reduce default processor count to two under CI environments Most CI implementations like travis / circleci run the builds containerised. This can lead to the situartion where many more processors are detected via /proc/cpuinfo and friends than are actually usable through resource limits enforced by the containerization. This can result in high resource consumption that might result in abnormal build termination. The default can easily be overriden in your CI setup. * http://fabiokung.com/2014/03/13/memory-inside-linux-containers/ 2014-08-11 17:52:51 +00:00			`describe '.ci?' do`
			`subject { object.ci? }`

Fix the use of instance doubles globally [fix #361] 2015-11-15 20:16:42 +00:00			`let(:value) { instance_double(Object, 'value') }`
Reduce default processor count to two under CI environments Most CI implementations like travis / circleci run the builds containerised. This can lead to the situartion where many more processors are detected via /proc/cpuinfo and friends than are actually usable through resource limits enforced by the containerization. This can result in high resource consumption that might result in abnormal build termination. The default can easily be overriden in your CI setup. * http://fabiokung.com/2014/03/13/memory-inside-linux-containers/ 2014-08-11 17:52:51 +00:00
			`before do`
Fix the use of instance doubles globally [fix #361] 2015-11-15 20:16:42 +00:00			`expect(ENV).to receive(:key?).with('CI').and_return(value)`
Reduce default processor count to two under CI environments Most CI implementations like travis / circleci run the builds containerised. This can lead to the situartion where many more processors are detected via /proc/cpuinfo and friends than are actually usable through resource limits enforced by the containerization. This can result in high resource consumption that might result in abnormal build termination. The default can easily be overriden in your CI setup. * http://fabiokung.com/2014/03/13/memory-inside-linux-containers/ 2014-08-11 17:52:51 +00:00			`end`

Fix the use of instance doubles globally [fix #361] 2015-11-15 20:16:42 +00:00			`it { should be(value) }`
Reduce default processor count to two under CI environments Most CI implementations like travis / circleci run the builds containerised. This can lead to the situartion where many more processors are detected via /proc/cpuinfo and friends than are actually usable through resource limits enforced by the containerization. This can result in high resource consumption that might result in abnormal build termination. The default can easily be overriden in your CI setup. * http://fabiokung.com/2014/03/13/memory-inside-linux-containers/ 2014-08-11 17:52:51 +00:00			`end`
Use more modern spec layout * This specs still have spec per method granularity * But one file specs multiple methods * Compatible with mutant spec selector * Deduplicates boilerplate unit setup 2013-12-29 23:29:58 +01:00			`end`