relevance-test-spec 0.4.0.5 → 0.4.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (5) hide show
  1. data/README.rdoc +5 -1
  2. data/Rakefile +2 -1
  3. data/lib/test/spec/version.rb +1 -1
  4. data/test-spec.gemspec +3 -3
  5. metadata +2 -2
data/README.rdoc CHANGED
@@ -6,7 +6,8 @@
6
6
  == What does this fork add?
7
7
 
8
8
  This is a fork to add some new features to make the dev experience nicer, and also to DRY up boilerplate
9
- that can appear in test/spec.
9
+ that can appear in test/spec. Note that this is a fork of the 0.4 release, as we haven't merged the 0.9
10
+ features back in yet.
10
11
 
11
12
  Specifically:
12
13
 
@@ -21,6 +22,7 @@ Specifically:
21
22
  * DRY'er, context-aware spec declarations for Rails projects. Very similiar to Rspec's Rails support:
22
23
 
23
24
  describe UsersController # Subclasses ActionController::TestCase and sets up the UsersController properly
25
+ describe UserMailer # Subclasses ActionMailer::TestCase
24
26
  describe User # Subclasses ActiveSupport::TestCase for model specs
25
27
 
26
28
 
@@ -353,6 +355,8 @@ Please mail bugs, suggestions and patches to
353
355
  Darcs repository ("darcs send" is welcome for patches):
354
356
  http://chneukirchen.org/repos/testspec
355
357
 
358
+ Continuous Integration at RunCodeRun:
359
+ http://runcoderun.com/relevance/test-spec
356
360
 
357
361
  == Thanks to
358
362
 
data/Rakefile CHANGED
@@ -20,7 +20,8 @@ echoe = Echoe.new('test-spec', Test::Spec::VERSION) do |p|
20
20
  test/spec is a clean-room implementation that maps most kinds of
21
21
  Test::Unit assertions to a `should'-like syntax.
22
22
 
23
- This is a fork of the main version to add some features and make thigns a bit easier for developers.
23
+ This is a fork of the main version to add some features and make things a bit easier for developers. It grew out of
24
+ day to day use at Relevance (http://thinkrelevance.com).
24
25
  EOF
25
26
  p.url = "http://github.com/relevance/test-spec"
26
27
  p.rdoc_pattern = /^(lib|bin|ext)|txt|rdoc|CHANGELOG|LICENSE|SPECS$/
data/lib/test/spec/version.rb CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  module Test
4
4
  module Spec
5
- VERSION = "0.4.0.5"
5
+ VERSION = "0.4.1"
6
6
  end
7
7
  end
8
8
 
data/test-spec.gemspec CHANGED
@@ -1,11 +1,11 @@
1
1
 
2
- # Gem::Specification for Test-spec-0.4.0.5
2
+ # Gem::Specification for Test-spec-0.4.1
3
3
  # Originally generated by Echoe
4
4
 
5
5
  --- !ruby/object:Gem::Specification
6
6
  name: test-spec
7
7
  version: !ruby/object:Gem::Version
8
- version: 0.4.0.5
8
+ version: 0.4.1
9
9
  platform: ruby
10
10
  authors:
11
11
  - Christian Neukirchen
@@ -45,7 +45,7 @@ dependencies:
45
45
  - !ruby/object:Gem::Version
46
46
  version: "0"
47
47
  version:
48
- description: test/spec layers an RSpec-inspired interface on top of Test::Unit, so you can mix TDD and BDD (Behavior-Driven Development). test/spec is a clean-room implementation that maps most kinds of Test::Unit assertions to a `should'-like syntax. This is a fork of the main version to add some features and make thigns a bit easier for developers.
48
+ description: test/spec layers an RSpec-inspired interface on top of Test::Unit, so you can mix TDD and BDD (Behavior-Driven Development). test/spec is a clean-room implementation that maps most kinds of Test::Unit assertions to a `should'-like syntax. This is a fork of the main version to add some features and make things a bit easier for developers. It grew out of day to day use at Relevance (http://thinkrelevance.com).
49
49
  email: chneukirchen@gmail.com
50
50
  executables:
51
51
  - specrb
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: relevance-test-spec
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.4.0.5
4
+ version: 0.4.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Christian Neukirchen
@@ -41,7 +41,7 @@ dependencies:
41
41
  - !ruby/object:Gem::Version
42
42
  version: "0"
43
43
  version:
44
- description: test/spec layers an RSpec-inspired interface on top of Test::Unit, so you can mix TDD and BDD (Behavior-Driven Development). test/spec is a clean-room implementation that maps most kinds of Test::Unit assertions to a `should'-like syntax. This is a fork of the main version to add some features and make thigns a bit easier for developers.
44
+ description: test/spec layers an RSpec-inspired interface on top of Test::Unit, so you can mix TDD and BDD (Behavior-Driven Development). test/spec is a clean-room implementation that maps most kinds of Test::Unit assertions to a `should'-like syntax. This is a fork of the main version to add some features and make things a bit easier for developers. It grew out of day to day use at Relevance (http://thinkrelevance.com).
45
45
  email: chneukirchen@gmail.com
46
46
  executables:
47
47
  - specrb