flatware-cucumber 2.2.1 → 2.3.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +3 -3
- metadata +4 -4
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 18b6fc74acf17af4c2686d351617988ca7d53f3b1a63a83ff730c8466d2069b4
|
|
4
|
+
data.tar.gz: 3c3527cbc838aad6ee3b4d61a94b34d51eb5e8c71f93a8195966b6a24f258374
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 01fb497ab669872e4229d2c2ba4fa9f5b7277e42e765b3a0109adeb0793ffcd5097b95f482251c0c68725cfa5b9e4991cbff4990d91e41afdd111099ff51170e
|
|
7
|
+
data.tar.gz: 291075b23841a94b27078aa7af6be9324a393969f7ea45d7b18fbff30dcdb7c68c1546a1f7fa45cc7d09df9358e12965c6453820ae14db982f186b1ad6506978
|
data/README.md
CHANGED
|
@@ -40,13 +40,13 @@ $ flatware rspec
|
|
|
40
40
|
|
|
41
41
|
The rspec runner can balance worker loads, making your suite even faster.
|
|
42
42
|
|
|
43
|
-
It forms
|
|
43
|
+
It forms balanced groups of spec files according to their last run times, if you've set `example_status_persistence_file_path` [in your RSpec config](https://relishapp.com/rspec/rspec-core/v/3-8/docs/command-line/only-failures).
|
|
44
44
|
|
|
45
|
-
For this to work the configuration option must be loaded before any specs are run. The `.rspec` file is one way to
|
|
45
|
+
For this to work the configuration option must be loaded before any specs are run. The `.rspec` file is one way to achieve this:
|
|
46
46
|
|
|
47
47
|
--require spec_helper
|
|
48
48
|
|
|
49
|
-
But beware, if you're using ActiveRecord in your suite you'll need to avoid doing things that cause it to establish a database connection in `spec_helper.rb`. If ActiveRecord connects before flatware forks off workers, each will die messily. All of this will just work if you're following [the
|
|
49
|
+
But beware, if you're using ActiveRecord in your suite you'll need to avoid doing things that cause it to establish a database connection in `spec_helper.rb`. If ActiveRecord connects before flatware forks off workers, each will die messily. All of this will just work if you're following [the recommended pattern of splitting your helpers into `spec_helper` and `rails_helper`](https://github.com/rspec/rspec-rails/blob/v3.8.2/lib/generators/rspec/install/templates/spec/rails_helper.rb). Another option is to use [the configurable hooks](
|
|
50
50
|
#faster-startup-with-activerecord
|
|
51
51
|
).
|
|
52
52
|
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: flatware-cucumber
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 2.2
|
|
4
|
+
version: 2.3.2
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Brian Dunn
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2024-
|
|
11
|
+
date: 2024-05-17 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: cucumber
|
|
@@ -30,14 +30,14 @@ dependencies:
|
|
|
30
30
|
requirements:
|
|
31
31
|
- - '='
|
|
32
32
|
- !ruby/object:Gem::Version
|
|
33
|
-
version: 2.2
|
|
33
|
+
version: 2.3.2
|
|
34
34
|
type: :runtime
|
|
35
35
|
prerelease: false
|
|
36
36
|
version_requirements: !ruby/object:Gem::Requirement
|
|
37
37
|
requirements:
|
|
38
38
|
- - '='
|
|
39
39
|
- !ruby/object:Gem::Version
|
|
40
|
-
version: 2.2
|
|
40
|
+
version: 2.3.2
|
|
41
41
|
description: A distributed cucumber runner
|
|
42
42
|
email: brian@hashrocket.com
|
|
43
43
|
executables: []
|