flatware-cucumber 2.1.0 → 2.2.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +27 -1
  3. metadata +6 -6
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: d9087029e790182b87ead8d50e2120731693ecafe726ac5b51a8396bc915d2ed
4
- data.tar.gz: 17e8e8709f9124acfbc80267d4b5b76d4ea97e2a8b48567a326d2dc046e9a495
3
+ metadata.gz: c596906fbb5c21b89f1bb885b4e04632de36415541dde7cfa7f53d6622c4601d
4
+ data.tar.gz: 3af7f17b6fb4c4bde7e176227244d550ac57093f19bdcc3c91823e46f26d09c7
5
5
  SHA512:
6
- metadata.gz: ba68d0fdb44bcca6f8321a9b8112c4dd02a0f055b7fc561bbe5c878d48956bfc0bd3c0078c46f834063a7db4fc8011bae9fbc6d17c21c6e8ae94ff4c3fdc61c5
7
- data.tar.gz: 79a8dc5c186c4cbc7220ec1fa1559e41b294e61ae65894087b67c596c851664b5f62405fe1feb3d026a3a794c01743a54dbc630c102c6e64384348cac39f8351
6
+ metadata.gz: 9602bd544c48fe8a2f0a683da8c14b0373f3ffb32b8aeb829e0a798dc12553ed8a58e3054ece968db91b6c5b4416a530d391563f08467be8d736f8e714cba21a
7
+ data.tar.gz: 9c817d17477ab2e5b6e22dd321f7c886d67e318d79ed556155264eca9d8169a01ee969afdb6b5c61c2b8d7f1fdaaa3564cd2a94ed53467369ac312fd99c948af
data/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Flatware [![Code Climate][code-climate-badge]][code-climate]
2
2
 
3
- [code-climate-badge]: https://codeclimate.com/github/briandunn/flatware.png
3
+ [code-climate-badge]: https://codeclimate.com/github/briandunn/flatware.svg
4
4
  [code-climate]: https://codeclimate.com/github/briandunn/flatware
5
5
 
6
6
  Flatware parallelizes your test suite to significantly reduce test time.
@@ -106,6 +106,11 @@ Flatware has a couple lifecycle callbacks that you can use to avoid booting your
106
106
  over again on every core. One way to take advantage of this via a `spec/flatware_helper.rb` file like so:
107
107
 
108
108
  ```ruby
109
+ ##
110
+ # uncomment if you get a segmentation fault from the "pg" gem
111
+ # @see https://github.com/ged/ruby-pg/issues/311#issuecomment-1609970533
112
+ # ENV["PGGSSENCMODE"] = "disable"
113
+
109
114
  Flatware.configure do |conf|
110
115
  conf.before_fork do
111
116
  require 'rails_helper'
@@ -114,6 +119,11 @@ Flatware.configure do |conf|
114
119
  end
115
120
 
116
121
  conf.after_fork do |test_env_number|
122
+ ##
123
+ # uncomment if you're using SimpleCov and have started it in `rails_helper` as suggested here:
124
+ # @see https://github.com/simplecov-ruby/simplecov/tree/main?tab=readme-ov-file#use-it-with-any-framework
125
+ # SimpleCov.at_fork.call(test_env_number)
126
+
117
127
  config = ActiveRecord::Base.connection_db_config.configuration_hash
118
128
 
119
129
  ActiveRecord::Base.establish_connection(
@@ -126,6 +136,15 @@ end
126
136
  ```
127
137
  Now when I run `bundle exec flatware rspec -r ./spec/flatware_helper` My app only boots once, rather than once per core.
128
138
 
139
+ ## SimpleCov
140
+
141
+ If you're using SimpleCov, follow [their directions](https://github.com/simplecov-ruby/simplecov/tree/main?tab=readme-ov-file#use-it-with-any-framework) to install. When you have it working as desired for serial runs, add
142
+ `SimpleCov.at_fork.call(test_env_number)` to flatware's `after_fork` hook. You should now get the same coverage stats from parallel and serial runs.
143
+
144
+ ## Segmentation faults in the PG gem
145
+
146
+ If you get a segmentation fault on start you may need to add `ENV["PGGSSENCMODE"] = "disable"` to the top of your flatware helper.
147
+
129
148
  ## Design Goals
130
149
 
131
150
  ### Maintainable
@@ -170,3 +189,10 @@ Do whatever you want. I'd love to help make sure Flatware meets your needs.
170
189
  [![Hashrocket logo](https://hashrocket.com/hashrocket_logo.svg)](https://hashrocket.com)
171
190
 
172
191
  Flatware is supported by the team at [Hashrocket](https://hashrocket.com), a multidisciplinary design & development consultancy. If you'd like to [work with us](https://hashrocket.com/contact-us/hire-us) or [join our team](https://hashrocket.com/contact-us/jobs), don't hesitate to get in touch.
192
+
193
+
194
+ # TODO:
195
+
196
+ possible simplecov fixes
197
+
198
+ 1. seems like we won't get the same results as serial rspec runs unless we start simplecov after fork. And if we do that, I think a process needs to claim to be the last one for simplecov to run the merge.
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.1.0
4
+ version: 2.2.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Brian Dunn
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2023-03-15 00:00:00.000000000 Z
11
+ date: 2024-03-02 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.1.0
33
+ version: 2.2.1
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.1.0
40
+ version: 2.2.1
41
41
  description: A distributed cucumber runner
42
42
  email: brian@hashrocket.com
43
43
  executables: []
@@ -72,14 +72,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
72
72
  version: '2.6'
73
73
  - - "<"
74
74
  - !ruby/object:Gem::Version
75
- version: '3.3'
75
+ version: '3.4'
76
76
  required_rubygems_version: !ruby/object:Gem::Requirement
77
77
  requirements:
78
78
  - - ">="
79
79
  - !ruby/object:Gem::Version
80
80
  version: '0'
81
81
  requirements: []
82
- rubygems_version: 3.3.7
82
+ rubygems_version: 3.4.1
83
83
  signing_key:
84
84
  specification_version: 4
85
85
  summary: A distributed cucumber runner