flatware-rspec 2.1.0 → 2.2.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +27 -1
- metadata +6 -6
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 51cfb243e84b6aa7021c6782841bc4158a637c30d078a47aa11c722440bf4723
|
|
4
|
+
data.tar.gz: 599dbbc3eba7f6ecd54265d250822fa5c8dd76e9a6ac8385be6b61f6cda90da0
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: ba4da5e82e22c8247e73e17c552a2ff4bf3f8c3e488680f5df88690f211c5923dba7ba4261cb8ad80bcd4c74da6306e284ced5571c5efec921c217afdc98ed29
|
|
7
|
+
data.tar.gz: ef7bb7799fa67a296a27922ba0511231e5b56153995fa02503de31411d0349caa6b26f2a20fd6dea613a412f5364550e3ec4acb5f1fc1f321eb54006b6ca9703
|
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.
|
|
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
|
[](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-rspec
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 2.1
|
|
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:
|
|
11
|
+
date: 2024-03-02 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: flatware
|
|
@@ -16,14 +16,14 @@ dependencies:
|
|
|
16
16
|
requirements:
|
|
17
17
|
- - '='
|
|
18
18
|
- !ruby/object:Gem::Version
|
|
19
|
-
version: 2.1
|
|
19
|
+
version: 2.2.1
|
|
20
20
|
type: :runtime
|
|
21
21
|
prerelease: false
|
|
22
22
|
version_requirements: !ruby/object:Gem::Requirement
|
|
23
23
|
requirements:
|
|
24
24
|
- - '='
|
|
25
25
|
- !ruby/object:Gem::Version
|
|
26
|
-
version: 2.1
|
|
26
|
+
version: 2.2.1
|
|
27
27
|
- !ruby/object:Gem::Dependency
|
|
28
28
|
name: rspec
|
|
29
29
|
requirement: !ruby/object:Gem::Requirement
|
|
@@ -79,14 +79,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
|
79
79
|
version: '2.6'
|
|
80
80
|
- - "<"
|
|
81
81
|
- !ruby/object:Gem::Version
|
|
82
|
-
version: '3.
|
|
82
|
+
version: '3.4'
|
|
83
83
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
|
84
84
|
requirements:
|
|
85
85
|
- - ">="
|
|
86
86
|
- !ruby/object:Gem::Version
|
|
87
87
|
version: '0'
|
|
88
88
|
requirements: []
|
|
89
|
-
rubygems_version: 3.
|
|
89
|
+
rubygems_version: 3.4.1
|
|
90
90
|
signing_key:
|
|
91
91
|
specification_version: 4
|
|
92
92
|
summary: A distributed rspec runner
|