right_support 2.8.12 → 2.8.15
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/.rspec +0 -1
- data/Gemfile +15 -21
- data/Gemfile.lock +59 -83
- data/Rakefile +0 -4
- data/VERSION +1 -1
- data/features/hash_tools.feature +27 -0
- data/features/step_definitions/hash_tools_steps.rb +41 -0
- data/lib/right_support/db/cassandra_model.rb +123 -109
- data/lib/right_support/log/mixin.rb +9 -2
- data/lib/right_support/rack/request_logger.rb +41 -28
- data/right_support.gemspec +14 -31
- data/right_support.rconf +4 -2
- data/spec/db/cassandra_model_part1_spec.rb +1 -1
- data/spec/db/cassandra_model_spec.rb +2 -2
- data/spec/log/mixin_spec.rb +29 -0
- data/spec/net/request_balancer_spec.rb +0 -1
- data/spec/rack/request_logger_spec.rb +39 -0
- data/spec/spec_helper.rb +0 -3
- metadata +36 -106
- data/features/continuous_integration.feature +0 -51
- data/features/continuous_integration_cucumber.feature +0 -28
- data/features/continuous_integration_rspec1.feature +0 -28
- data/features/continuous_integration_rspec2.feature +0 -28
@@ -1,51 +0,0 @@
|
|
1
|
-
Feature: continuous integration disabled
|
2
|
-
In order to let minimize runtime dependencies
|
3
|
-
RightSupport's Rake CI harness should gracefully handle missing gems
|
4
|
-
So it runs predictably and reliably in production
|
5
|
-
|
6
|
-
Background:
|
7
|
-
Given a Ruby application
|
8
|
-
And a Gemfile
|
9
|
-
And a gem dependency on 'rake ~> 0.9'
|
10
|
-
|
11
|
-
Scenario: all gems unavailable
|
12
|
-
Given the Rakefile contains a RightSupport::CI::RakeTask
|
13
|
-
When I install the bundle
|
14
|
-
And I rake '-T'
|
15
|
-
Then the output should not contain 'ci:cucumber'
|
16
|
-
And the output should not contain 'ci:spec'
|
17
|
-
|
18
|
-
Scenario: conditional availability of ci:cucumber
|
19
|
-
Given a gem dependency on 'rspec ~> 1.0'
|
20
|
-
And a gem dependency on 'builder ~> 3.0'
|
21
|
-
And the Rakefile contains a RightSupport::CI::RakeTask
|
22
|
-
When I install the bundle
|
23
|
-
And I rake '-T'
|
24
|
-
Then the output should contain 'ci:spec'
|
25
|
-
And the output should not contain 'ci:cucumber'
|
26
|
-
|
27
|
-
Scenario: conditional availability of ci:rspec
|
28
|
-
Given a gem dependency on 'cucumber ~> 1.0'
|
29
|
-
And the Rakefile contains a RightSupport::CI::RakeTask
|
30
|
-
When I install the bundle
|
31
|
-
And I rake '-T'
|
32
|
-
Then the output should contain 'ci:cucumber'
|
33
|
-
And the output should not contain 'ci:spec'
|
34
|
-
|
35
|
-
Scenario: list Rake tasks
|
36
|
-
Given a gem dependency on 'rspec ~> 2.0'
|
37
|
-
And a gem dependency on 'cucumber ~> 1.0'
|
38
|
-
And the Rakefile contains a RightSupport::CI::RakeTask
|
39
|
-
When I install the bundle
|
40
|
-
And I rake '-T'
|
41
|
-
And the output should contain 'ci:cucumber'
|
42
|
-
And the output should contain 'ci:spec'
|
43
|
-
|
44
|
-
Scenario: override namespace
|
45
|
-
Given a gem dependency on 'rspec ~> 2.0'
|
46
|
-
And a gem dependency on 'cucumber ~> 1.0'
|
47
|
-
And the Rakefile contains a RightSupport::CI::RakeTask with parameter ':funkalicious'
|
48
|
-
When I install the bundle
|
49
|
-
And I rake '-T'
|
50
|
-
Then the output should contain 'funkalicious:cucumber'
|
51
|
-
Then the output should contain 'funkalicious:spec'
|
@@ -1,28 +0,0 @@
|
|
1
|
-
Feature: continuous integration of Cucumber features
|
2
|
-
In order to facilitate TDD and enhance code quality
|
3
|
-
RightSupport should provide CI tasks with Cucumber with JUnit XML output
|
4
|
-
So any Ruby project can have a beautiful, info-rich Jenkins project
|
5
|
-
|
6
|
-
Background:
|
7
|
-
Given a Ruby application
|
8
|
-
And a Gemfile
|
9
|
-
And a gem dependency on 'rake ~> 0.9'
|
10
|
-
And a gem dependency on 'builder ~> 3.0'
|
11
|
-
And a gem dependency on 'cucumber ~> 1.0'
|
12
|
-
And the Rakefile contains a RightSupport::CI::RakeTask
|
13
|
-
|
14
|
-
Scenario: passing Cucumber features
|
15
|
-
Given a trivial Cucumber feature
|
16
|
-
When I install the bundle
|
17
|
-
And I rake 'ci:cucumber'
|
18
|
-
Then the command should succeed
|
19
|
-
And the output should contain '** Execute ci:cucumber'
|
20
|
-
And the directory 'measurement/cucumber' should contain files
|
21
|
-
|
22
|
-
Scenario: failing Cucumber features
|
23
|
-
Given a trivial failing Cucumber feature
|
24
|
-
When I install the bundle
|
25
|
-
And I rake 'ci:cucumber'
|
26
|
-
Then the command should fail
|
27
|
-
And the output should contain '** Execute ci:cucumber'
|
28
|
-
And the directory 'measurement/cucumber' should contain files
|
@@ -1,28 +0,0 @@
|
|
1
|
-
Feature: continuous integration of RSpec 1.x specs
|
2
|
-
In order to facilitate TDD and enhance code quality
|
3
|
-
RightSupport should provide a Rake CI harness with JUnit XML output
|
4
|
-
So any Ruby project can have a beautiful, info-rich Jenkins project
|
5
|
-
|
6
|
-
Background:
|
7
|
-
Given a Ruby application
|
8
|
-
And a Gemfile
|
9
|
-
And a gem dependency on 'rake ~> 0.9'
|
10
|
-
And a gem dependency on 'rspec ~> 1.0'
|
11
|
-
And a gem dependency on 'builder ~> 3.0'
|
12
|
-
And the Rakefile contains a RightSupport::CI::RakeTask
|
13
|
-
|
14
|
-
Scenario: passing RSpec 1.x examples
|
15
|
-
Given a trivial RSpec spec
|
16
|
-
When I install the bundle
|
17
|
-
And I rake 'ci:spec'
|
18
|
-
Then the command should succeed
|
19
|
-
And the file 'measurement/rspec/rspec.xml' should mention 2 passing test cases
|
20
|
-
And the file 'measurement/rspec/rspec.xml' should mention 0 failing test cases
|
21
|
-
|
22
|
-
Scenario: failing RSpec 1.x examples
|
23
|
-
Given a trivial failing RSpec spec
|
24
|
-
When I install the bundle
|
25
|
-
And I rake 'ci:spec'
|
26
|
-
Then the command should fail
|
27
|
-
And the file 'measurement/rspec/rspec.xml' should mention 2 passing test cases
|
28
|
-
And the file 'measurement/rspec/rspec.xml' should mention 1 failing test case
|
@@ -1,28 +0,0 @@
|
|
1
|
-
Feature: continuous integration of RSpec 2.x specs
|
2
|
-
In order to facilitate TDD and enhance code quality
|
3
|
-
RightSupport should provide a Rake CI harness with JUnit XML output
|
4
|
-
So any Ruby project can have a beautiful, info-rich Jenkins project
|
5
|
-
|
6
|
-
Background:
|
7
|
-
Given a Ruby application
|
8
|
-
And a Gemfile
|
9
|
-
And a gem dependency on 'rake ~> 0.9'
|
10
|
-
And a gem dependency on 'rspec ~> 2.0'
|
11
|
-
And a gem dependency on 'builder ~> 3.0'
|
12
|
-
And the Rakefile contains a RightSupport::CI::RakeTask
|
13
|
-
|
14
|
-
Scenario: passing examples
|
15
|
-
And a trivial RSpec spec
|
16
|
-
When I install the bundle
|
17
|
-
And I rake 'ci:spec'
|
18
|
-
Then the command should succeed
|
19
|
-
And the file 'measurement/rspec/rspec.xml' should mention 2 passing test cases
|
20
|
-
And the file 'measurement/rspec/rspec.xml' should mention 0 failing test cases
|
21
|
-
|
22
|
-
Scenario: failing examples
|
23
|
-
And a trivial failing RSpec spec
|
24
|
-
When I install the bundle
|
25
|
-
And I rake 'ci:spec'
|
26
|
-
Then the command should fail
|
27
|
-
And the file 'measurement/rspec/rspec.xml' should mention 2 passing test cases
|
28
|
-
And the file 'measurement/rspec/rspec.xml' should mention 1 failing test case
|