Sha256: 2f8695ed6f603d8ce82c0a70c2de5159ebb22e48e86025c4f044a4c89508129e
Contents?: true
Size: 1.93 KB
Versions: 3
Compression:
Stored size: 1.93 KB
Contents
Feature: spec/spec.opts
For backwards compatibility with rspec-1, you can write command
line options in a spec/spec.opts file and it will be loaded
automatically.
Options declared in spec/spec.opts will override configuration
set up in Rspec.configure blocks.
Scenario: color set in Rspec.configure
Given a file named "spec/example_spec.rb" with:
"""
Rspec.configure {|c| c.color_enabled = true }
describe "color_enabled" do
context "when set with Rspec.configure" do
it "is true" do
Rspec.configuration.color_enabled?.should be_true
end
end
end
"""
When I run "rspec spec/example_spec.rb"
Then I should see "1 example, 0 failures"
Scenario: color set in .rspec
Given a file named ".rspec" with:
"""
--color
"""
And a file named "spec/example_spec.rb" with:
"""
describe "color_enabled" do
context "when set with Rspec.configure" do
it "is true" do
Rspec.configuration.color_enabled?.should be_true
end
end
end
"""
When I run "rspec spec/example_spec.rb"
Then I should see "1 example, 0 failures"
@wip
Scenario: formatter set in both (.rspec wins)
Given a file named ".rspec" with:
"""
--format documentation
"""
And a file named "spec/spec_helper.rb" with:
"""
Rspec.configure {|c| c.formatter = 'progress'}
"""
And a file named "spec/example_spec.rb" with:
"""
require "spec_helper"
describe "formatter" do
context "when set with Rspec.configure and in spec.opts" do
it "takes the value set in spec.opts" do
Rspec.configuration.formatter.should be_an(Rspec::Core::Formatters::DocumentationFormatter)
end
end
end
"""
When I run "rspec spec/example_spec.rb"
Then I should see "1 example, 0 failures"
Version data entries
3 entries across 3 versions & 1 rubygems