rspec-rerun 0.1.0 → 0.1.1
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/README.md +11 -8
- data/lib/rspec-rerun/version.rb +1 -1
- data/lib/tasks/rspec.rake +2 -0
- metadata +3 -3
data/README.md
CHANGED
@@ -1,15 +1,18 @@
|
|
1
|
-
|
2
|
-
===========
|
1
|
+

|
3
2
|
|
4
|
-
|
3
|
+
[](http://travis-ci.org/dblock/rspec-rerun)
|
4
|
+
|
5
|
+
The **rspec-rerun** gem is a drop-in solution to retry (rerun) failed RSpec examples. It may be useful, for example, with finicky Capybara tests. The strategy to rerun failed specs is to output a file called `rspec.failures` that contains a list of failed examples and to feed that file back to RSpec via `-e`.
|
5
6
|
|
6
7
|
Usage
|
7
8
|
-----
|
8
9
|
|
9
|
-
Add `rspec-rerun` to `Gemfile
|
10
|
+
Add `rspec-rerun` to `Gemfile` in the `:development` and `:test` groups.
|
10
11
|
|
11
12
|
``` ruby
|
12
|
-
|
13
|
+
group :development, :test do
|
14
|
+
gem "rspec-rerun"
|
15
|
+
end
|
13
16
|
```
|
14
17
|
|
15
18
|
Require `rspec-rerun` and change the default task in `Rakefile`.
|
@@ -19,14 +22,14 @@ require 'rspec-rerun'
|
|
19
22
|
task :default => "rspec-rerun:spec"
|
20
23
|
```
|
21
24
|
|
25
|
+
Run `rake` or `rake rspec-rerun:spec`. Failed examples will be rerun automatically.
|
26
|
+
|
22
27
|
It might also be a good idea to add `rspec.failures` to `.gitignore`.
|
23
28
|
|
24
29
|
History
|
25
30
|
-------
|
26
31
|
|
27
|
-
Rerunning failed specs has been a long requested feature
|
28
|
-
|
29
|
-
The *rspec-rerun* gem is an attempt to package the parts that didn't make it into rspec-core.
|
32
|
+
Rerunning failed specs has been a long requested feature [#456](https://github.com/rspec/rspec-core/issues/456) in [RSpec](https://github.com/rspec/rspec-core/). A viable approach was suggested in [#596](https://github.com/rspec/rspec-core/pull/596). The infrastructure from that pull request was merged and released with rspec-core 2.11, which enabled re-running specs outside of RSpec, as described in [our blog post](http://artsy.github.com/blog/2012/05/15/how-to-organize-over-3000-rspec-specs-and-retry-test-failures/). This gem has evolved from it.
|
30
33
|
|
31
34
|
Contributing
|
32
35
|
------------
|
data/lib/rspec-rerun/version.rb
CHANGED
data/lib/tasks/rspec.rake
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: rspec-rerun
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.1.
|
4
|
+
version: 0.1.1
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -9,7 +9,7 @@ authors:
|
|
9
9
|
autorequire:
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
|
-
date: 2012-08-
|
12
|
+
date: 2012-08-16 00:00:00.000000000 Z
|
13
13
|
dependencies:
|
14
14
|
- !ruby/object:Gem::Dependency
|
15
15
|
name: rspec
|
@@ -104,7 +104,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
104
104
|
version: '0'
|
105
105
|
segments:
|
106
106
|
- 0
|
107
|
-
hash:
|
107
|
+
hash: 4393298230881452392
|
108
108
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
109
109
|
none: false
|
110
110
|
requirements:
|