rspec-block_is_expected 1.0.4 → 1.0.5
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- checksums.yaml.gz.sig +4 -0
- data/CHANGELOG.md +14 -0
- data/CODE_OF_CONDUCT.md +57 -47
- data/CONTRIBUTING.md +36 -0
- data/{LICENSE → LICENSE.txt} +1 -1
- data/README.md +89 -67
- data/lib/rspec/block_is_expected/matchers/not.rb +4 -4
- data/lib/rspec/block_is_expected/rspec.rb +2 -2
- data/lib/rspec/block_is_expected/version.rb +1 -1
- data/lib/rspec/block_is_expected.rb +2 -2
- data.tar.gz.sig +1 -0
- metadata +38 -133
- metadata.gz.sig +0 -0
- data/.gitignore +0 -15
- data/.rspec +0 -3
- data/.rubocop.yml +0 -52
- data/.rubocop_todo.yml +0 -32
- data/.tool-versions +0 -1
- data/.travis.yml +0 -61
- data/Appraisals +0 -32
- data/Gemfile +0 -22
- data/Gemfile.lock +0 -107
- data/Rakefile +0 -29
- data/bin/console +0 -14
- data/bin/setup +0 -8
- data/gemfiles/jruby_1.7.26.gemfile +0 -16
- data/gemfiles/jruby_9.1.9.0.gemfile +0 -15
- data/gemfiles/jruby_9.2.0.0.gemfile +0 -15
- data/gemfiles/jruby_head.gemfile +0 -15
- data/gemfiles/ruby_1.8.7_p374.gemfile +0 -16
- data/gemfiles/ruby_1.9.3_p551.gemfile +0 -16
- data/gemfiles/ruby_2.0.0_p648.gemfile +0 -16
- data/gemfiles/ruby_2.1.10.gemfile +0 -15
- data/gemfiles/ruby_2.2.10.gemfile +0 -16
- data/gemfiles/ruby_2.3.7.gemfile +0 -16
- data/gemfiles/ruby_2.4.4.gemfile +0 -16
- data/gemfiles/ruby_2.5.1.gemfile +0 -16
- data/gemfiles/ruby_head.gemfile +0 -16
- data/rspec-block_is_expected.gemspec +0 -41
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 61309d40f2a932928d07386ca56fe0a80091e24a9f60bb1767b8855d7d6a11cb
|
|
4
|
+
data.tar.gz: 51796a1ce8d0fb98cbe00f04966e6519944d9ee9b9ef3b67b2dd2e984c5cc81a
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 42adf2f35405d09ce84cd8dd52f90b404086de51c6f9b009dc5640530684d3f4dcfbbc440289ad016321856a8792a6ec9e3b979a060bbdfc9840730c6d8c862b
|
|
7
|
+
data.tar.gz: 8a0bfb4c4854c72b021f0034aa85a80116317532f65438a8707c488890d2fcabe80e8dcdce5e21db8351ee3f112a488cc5abfa8479b68f1bca9d14dcdaa42ed4
|
checksums.yaml.gz.sig
ADDED
|
@@ -0,0 +1,4 @@
|
|
|
1
|
+
~:�D��Z���7�� �:�|��7aW�KR8��)!B�3�NA,�f��j�`Zs'�EّSp\�����Q�� 6a';1g�8�7n���S:ئ���
|
|
2
|
+
Z��@_N�, �.L=`�� H͊�JZ��Գ�)*�B(>�Y���Cɫf�/�K���p��;P2�.X�5yg6-�
|
|
3
|
+
KF��Hީ�w�Buy��0Úhj��&B�7�~�ۻr=]�=F���t�x%j��)� ���30���7��=T�o����Е ��q{C; N}�h
|
|
4
|
+
,-XQQ�D�"�e���M���.����I"X
|
|
5
|
��Vg��T����X ]�LQ���࣊�XC���Az���8IkJ�
|
data/CHANGELOG.md
CHANGED
|
@@ -10,9 +10,23 @@ and this project adheres to [Semantic Versioning v2](https://semver.org/spec/v2.
|
|
|
10
10
|
### Fixed
|
|
11
11
|
### Removed
|
|
12
12
|
|
|
13
|
+
## [1.0.5] - 2023-04-01
|
|
14
|
+
### Added
|
|
15
|
+
- Structured gemfiles
|
|
16
|
+
- Rubocop with standard, gradual, & more
|
|
17
|
+
- Releases are now signed
|
|
18
|
+
- Releases now have checksums
|
|
19
|
+
### Changed
|
|
20
|
+
- TravisCI => GitHub Actions
|
|
21
|
+
- CODE_OF_CONDUCT.md upgraded to v2.0
|
|
22
|
+
- Moved from master to main default branch
|
|
23
|
+
### Fixed
|
|
24
|
+
- README Badges (CI status)
|
|
25
|
+
|
|
13
26
|
## [1.0.4] - 2023-03-23
|
|
14
27
|
### Added
|
|
15
28
|
- Required ruby version in gemspec >= 1.8.7
|
|
29
|
+
- not bumping major version, because this was already the de-facto minimum
|
|
16
30
|
### Changed
|
|
17
31
|
- Moved rubocop config to root
|
|
18
32
|
### Fixed
|
data/CODE_OF_CONDUCT.md
CHANGED
|
@@ -2,73 +2,83 @@
|
|
|
2
2
|
|
|
3
3
|
## Our Pledge
|
|
4
4
|
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
size, disability, ethnicity, gender identity and expression, level of experience,
|
|
9
|
-
nationality, personal appearance, race, religion, or sexual identity and
|
|
10
|
-
orientation.
|
|
5
|
+
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
|
|
6
|
+
|
|
7
|
+
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
|
|
11
8
|
|
|
12
9
|
## Our Standards
|
|
13
10
|
|
|
14
|
-
Examples of behavior that contributes to
|
|
15
|
-
include:
|
|
11
|
+
Examples of behavior that contributes to a positive environment for our community include:
|
|
16
12
|
|
|
17
|
-
*
|
|
18
|
-
* Being respectful of differing viewpoints and experiences
|
|
19
|
-
*
|
|
20
|
-
*
|
|
21
|
-
*
|
|
13
|
+
* Demonstrating empathy and kindness toward other people
|
|
14
|
+
* Being respectful of differing opinions, viewpoints, and experiences
|
|
15
|
+
* Giving and gracefully accepting constructive feedback
|
|
16
|
+
* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
|
|
17
|
+
* Focusing on what is best not just for us as individuals, but for the overall community
|
|
22
18
|
|
|
23
|
-
Examples of unacceptable behavior
|
|
19
|
+
Examples of unacceptable behavior include:
|
|
24
20
|
|
|
25
|
-
* The use of sexualized language or imagery and
|
|
26
|
-
advances
|
|
27
|
-
* Trolling, insulting
|
|
21
|
+
* The use of sexualized language or imagery, and sexual attention or
|
|
22
|
+
advances of any kind
|
|
23
|
+
* Trolling, insulting or derogatory comments, and personal or political attacks
|
|
28
24
|
* Public or private harassment
|
|
29
|
-
* Publishing others' private information, such as a physical or
|
|
30
|
-
address, without explicit permission
|
|
25
|
+
* Publishing others' private information, such as a physical or email
|
|
26
|
+
address, without their explicit permission
|
|
31
27
|
* Other conduct which could reasonably be considered inappropriate in a
|
|
32
28
|
professional setting
|
|
33
29
|
|
|
34
|
-
##
|
|
30
|
+
## Enforcement Responsibilities
|
|
35
31
|
|
|
36
|
-
|
|
37
|
-
behavior and are expected to take appropriate and fair corrective action in
|
|
38
|
-
response to any instances of unacceptable behavior.
|
|
32
|
+
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
|
|
39
33
|
|
|
40
|
-
|
|
41
|
-
reject comments, commits, code, wiki edits, issues, and other contributions
|
|
42
|
-
that are not aligned to this Code of Conduct, or to ban temporarily or
|
|
43
|
-
permanently any contributor for other behaviors that they deem inappropriate,
|
|
44
|
-
threatening, offensive, or harmful.
|
|
34
|
+
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
|
|
45
35
|
|
|
46
36
|
## Scope
|
|
47
37
|
|
|
48
|
-
This Code of Conduct applies
|
|
49
|
-
when an individual is representing the project or its community. Examples of
|
|
50
|
-
representing a project or community include using an official project e-mail
|
|
51
|
-
address, posting via an official social media account, or acting as an appointed
|
|
52
|
-
representative at an online or offline event. Representation of a project may be
|
|
53
|
-
further defined and clarified by project maintainers.
|
|
38
|
+
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
|
|
54
39
|
|
|
55
40
|
## Enforcement
|
|
56
41
|
|
|
57
|
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
42
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at peter.boling@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
|
|
43
|
+
|
|
44
|
+
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
|
|
45
|
+
|
|
46
|
+
## Enforcement Guidelines
|
|
47
|
+
|
|
48
|
+
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
|
|
49
|
+
|
|
50
|
+
### 1. Correction
|
|
51
|
+
|
|
52
|
+
**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
|
|
53
|
+
|
|
54
|
+
**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
|
|
55
|
+
|
|
56
|
+
### 2. Warning
|
|
57
|
+
|
|
58
|
+
**Community Impact**: A violation through a single incident or series of actions.
|
|
63
59
|
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
60
|
+
**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
|
|
61
|
+
|
|
62
|
+
### 3. Temporary Ban
|
|
63
|
+
|
|
64
|
+
**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
|
|
65
|
+
|
|
66
|
+
**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
|
|
67
|
+
|
|
68
|
+
### 4. Permanent Ban
|
|
69
|
+
|
|
70
|
+
**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
|
|
71
|
+
|
|
72
|
+
**Consequence**: A permanent ban from any sort of public interaction within the community.
|
|
67
73
|
|
|
68
74
|
## Attribution
|
|
69
75
|
|
|
70
|
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version
|
|
71
|
-
available at
|
|
76
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
|
|
77
|
+
available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
|
|
78
|
+
|
|
79
|
+
Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
|
|
80
|
+
|
|
81
|
+
[homepage]: https://www.contributor-covenant.org
|
|
72
82
|
|
|
73
|
-
|
|
74
|
-
|
|
83
|
+
For answers to common questions about this code of conduct, see the FAQ at
|
|
84
|
+
https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
|
data/CONTRIBUTING.md
ADDED
|
@@ -0,0 +1,36 @@
|
|
|
1
|
+
## Contributing
|
|
2
|
+
|
|
3
|
+
Bug reports and pull requests are welcome on GitLab at [https://gitlab.com/pboling/rspec-block_is_expected][🚎src-main]
|
|
4
|
+
. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to
|
|
5
|
+
the [code of conduct][conduct].
|
|
6
|
+
|
|
7
|
+
To submit a patch, please fork the project and create a patch with tests. Once you're happy with it send a pull request
|
|
8
|
+
and post a message to the [gitter chat][🏘chat].
|
|
9
|
+
|
|
10
|
+
## Release
|
|
11
|
+
|
|
12
|
+
To release a new version:
|
|
13
|
+
|
|
14
|
+
1. Run `bin/setup && bin/rake` as a tests, coverage, & linting sanity check.
|
|
15
|
+
2. update the version number in `version.rb`
|
|
16
|
+
3. run `bundle exec rake build:checksum`
|
|
17
|
+
4. move the built gem to project root
|
|
18
|
+
5. run `bin/checksum` to create the missing SHA256 checksum
|
|
19
|
+
6. move the built gem back to `pkg/`
|
|
20
|
+
7. commit the changes
|
|
21
|
+
8. run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org][rubygems].
|
|
22
|
+
|
|
23
|
+
NOTE: You will need to have a public key in `certs/`, and list your cert in the
|
|
24
|
+
`gemspec`, in order to sign the new release.
|
|
25
|
+
See: [RubyGems Security Guide][rubygems-security-guide]
|
|
26
|
+
|
|
27
|
+
## Contributors
|
|
28
|
+
|
|
29
|
+
See: [https://gitlab.com/pboling/rspec-block_is_expected/-/graphs/main][🖐contributors]
|
|
30
|
+
|
|
31
|
+
[conduct]: https://gitlab.com/pboling/rspec-block_is_expected/-/blob/main/CODE_OF_CONDUCT.md
|
|
32
|
+
[🖐contributors]: https://gitlab.com/pboling/rspec-block_is_expected/-/graphs/main
|
|
33
|
+
[🚎src-main]: https://gitlab.com/pboling/rspec-block_is_expected/-/tree/main
|
|
34
|
+
[🏘chat]: https://matrix.to/#/%23pboling_rspec-block_is_expected:gitter.im
|
|
35
|
+
[rubygems-security-guide]: https://guides.rubygems.org/security/#building-gems
|
|
36
|
+
[rubygems]: https://rubygems.org
|
data/{LICENSE → LICENSE.txt}
RENAMED
data/README.md
CHANGED
|
@@ -4,32 +4,39 @@ This gem does one very simple thing very well. It allows you to use `block_is_e
|
|
|
4
4
|
|
|
5
5
|
```ruby
|
|
6
6
|
subject { Integer(nil) }
|
|
7
|
-
it(
|
|
7
|
+
it("raises") { block_is_expected.to(raise_error(TypeError)) }
|
|
8
8
|
```
|
|
9
9
|
|
|
10
|
-
| Project
|
|
11
|
-
|
|
12
|
-
| gem name
|
|
13
|
-
| license
|
|
14
|
-
| download rank
|
|
15
|
-
| version
|
|
16
|
-
| dependencies
|
|
17
|
-
| continuous integration
|
|
18
|
-
| test coverage
|
|
19
|
-
| maintainability
|
|
20
|
-
| code triage
|
|
21
|
-
| homepage
|
|
22
|
-
| documentation
|
|
23
|
-
| Spread ~♡ⓛⓞⓥⓔ♡~
|
|
24
|
-
|
|
25
|
-
|
|
10
|
+
| Project | RSpec::BlockIsExpected |
|
|
11
|
+
|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
12
|
+
| gem name | [rspec-block_is_expected](https://rubygems.org/gems/rspec-block_is_expected) |
|
|
13
|
+
| license | [](https://opensource.org/licenses/MIT) |
|
|
14
|
+
| download rank | [](https://github.com/pboling/rspec-block_is_expected) |
|
|
15
|
+
| version | [](https://rubygems.org/gems/rspec-block_is_expected) |
|
|
16
|
+
| dependencies | [![Depfu][depfu-img]][depfu] |
|
|
17
|
+
| continuous integration | [![Current][🚎cwfi]][🚎cwf] [![Heads][🖐hwfi]][🖐hwf] [![Style][🧮swfi]][🧮swf] |
|
|
18
|
+
| test coverage | [![Test Coverage][cc-covi]][cc-cov] |
|
|
19
|
+
| maintainability | [](https://codeclimate.com/github/pboling/rspec-block_is_expected/maintainability) |
|
|
20
|
+
| code triage | [](https://www.codetriage.com/pboling/rspec-block_is_expected) |
|
|
21
|
+
| homepage | [on Github.com][homepage], [on Railsbling.com][blogpage] |
|
|
22
|
+
| documentation | [on RDoc.info][documentation] |
|
|
23
|
+
| Spread ~♡ⓛⓞⓥⓔ♡~ | [![Liberapay Goal Progress][⛳liberapay-img]][⛳liberapay], [🧊][🧊berg], [🛖][🛖hut], [🧪][🧪lab], [🌏][aboutme], [👼][angellist], [⚗️][devto], [![Tweet @galtzo][followme]][twitter] |
|
|
24
|
+
|
|
25
|
+
[🚎cwf]: https://github.com/pboling/rspec-block_is_expected/actions/workflows/current.yml
|
|
26
|
+
[🚎cwfi]: https://github.com/pboling/rspec-block_is_expected/actions/workflows/current.yml/badge.svg
|
|
27
|
+
[🖐hwf]: https://github.com/pboling/rspec-block_is_expected/actions/workflows/heads.yml
|
|
28
|
+
[🖐hwfi]: https://github.com/pboling/rspec-block_is_expected/actions/workflows/heads.yml/badge.svg
|
|
29
|
+
[🧮swf]: https://github.com/pboling/rspec-block_is_expected/actions/workflows/style.yml
|
|
30
|
+
[🧮swfi]: https://github.com/pboling/rspec-block_is_expected/actions/workflows/style.yml/badge.svg
|
|
31
|
+
|
|
32
|
+
If you only _ever_ want to test subjects wrapped in blocks, and are comfortable with **losing** the standard `is_expected` behavior, see an alternative to this gem [here](https://github.com/christopheraue/ruby-rspec-is_expected_block/).
|
|
26
33
|
|
|
27
34
|
## Installation
|
|
28
35
|
|
|
29
36
|
Add this line to your application's Gemfile:
|
|
30
37
|
|
|
31
38
|
```ruby
|
|
32
|
-
gem
|
|
39
|
+
gem "rspec-block_is_expected", :group => :test
|
|
33
40
|
```
|
|
34
41
|
|
|
35
42
|
And then execute:
|
|
@@ -46,7 +53,7 @@ There is no configuration needed if you your test suite loads the bundle group (
|
|
|
46
53
|
|
|
47
54
|
Otherwise, you may load it manually near the top of your `spec_helper.rb`, and it will self configure.
|
|
48
55
|
```ruby
|
|
49
|
-
require
|
|
56
|
+
require "rspec/block_is_expected"
|
|
50
57
|
```
|
|
51
58
|
|
|
52
59
|
### RSpec Matchers
|
|
@@ -56,15 +63,15 @@ but `to_not` doesn't work with multiple expectations.
|
|
|
56
63
|
So negated matchers are required. A basic set of them are included with this gem, and can be loaded with:
|
|
57
64
|
|
|
58
65
|
```ruby
|
|
59
|
-
require
|
|
66
|
+
require "rspec/block_is_expected/matchers/not"
|
|
60
67
|
```
|
|
61
68
|
|
|
62
69
|
This gives you the following matchers:
|
|
63
70
|
```ruby
|
|
64
|
-
RSpec::Matchers.define_negated_matcher
|
|
65
|
-
RSpec::Matchers.define_negated_matcher
|
|
66
|
-
RSpec::Matchers.define_negated_matcher
|
|
67
|
-
RSpec::Matchers.define_negated_matcher
|
|
71
|
+
RSpec::Matchers.define_negated_matcher(:not_change, :change)
|
|
72
|
+
RSpec::Matchers.define_negated_matcher(:not_include, :include)
|
|
73
|
+
RSpec::Matchers.define_negated_matcher(:not_eq, :eq)
|
|
74
|
+
RSpec::Matchers.define_negated_matcher(:not_raise_error, :raise_error)
|
|
68
75
|
```
|
|
69
76
|
|
|
70
77
|
#### Example
|
|
@@ -74,7 +81,7 @@ You have a module like this:
|
|
|
74
81
|
```ruby
|
|
75
82
|
module MyTasks
|
|
76
83
|
def my_rakelib
|
|
77
|
-
Rake.add_rakelib(
|
|
84
|
+
Rake.add_rakelib("bananas")
|
|
78
85
|
end
|
|
79
86
|
module_function :my_rakelib
|
|
80
87
|
end
|
|
@@ -83,14 +90,14 @@ end
|
|
|
83
90
|
You have a spec like this:
|
|
84
91
|
|
|
85
92
|
```ruby
|
|
86
|
-
require
|
|
93
|
+
require "rake"
|
|
87
94
|
|
|
88
95
|
RSpec.describe(MyTasks) do
|
|
89
|
-
describe
|
|
96
|
+
describe "my_rakelib" do
|
|
90
97
|
subject(:my_rakelib) { described_class.my_rakelib }
|
|
91
|
-
it
|
|
92
|
-
block_is_expected.to
|
|
93
|
-
|
|
98
|
+
it "updates rakelib" do
|
|
99
|
+
block_is_expected.to(not_raise_error &
|
|
100
|
+
change { Rake.application.options.rakelib }.from(["rakelib"]).to(%w[rakelib bananas]))
|
|
94
101
|
end
|
|
95
102
|
end
|
|
96
103
|
end
|
|
@@ -115,38 +122,48 @@ inherit_gem:
|
|
|
115
122
|
The spec suite for this gem has some examples of usage, lightly edited here.
|
|
116
123
|
|
|
117
124
|
```ruby
|
|
118
|
-
RSpec.describe
|
|
119
|
-
context
|
|
125
|
+
RSpec.describe("TestyMcTest") do
|
|
126
|
+
context "errors raised" do
|
|
120
127
|
subject { Integer(nil) }
|
|
121
|
-
it(
|
|
128
|
+
it("can be tested") do
|
|
122
129
|
# Where you used to have:
|
|
123
130
|
# expect { subject }.to raise_error(TypeError)
|
|
124
|
-
block_is_expected.to
|
|
131
|
+
block_is_expected.to(raise_error(TypeError))
|
|
125
132
|
end
|
|
126
133
|
end
|
|
127
|
-
context
|
|
134
|
+
context "execution" do
|
|
128
135
|
let(:mutex) { Mutex.new }
|
|
129
136
|
subject { mutex.lock }
|
|
130
|
-
it(
|
|
131
|
-
expect(mutex.locked?).to
|
|
137
|
+
it("can change state") do
|
|
138
|
+
expect(mutex.locked?).to(eq(false))
|
|
132
139
|
# Where you used to have:
|
|
133
140
|
# expect { subject }.to_not raise_error
|
|
134
|
-
block_is_expected.to_not
|
|
135
|
-
expect(mutex.locked?).to
|
|
141
|
+
block_is_expected.to_not(raise_error)
|
|
142
|
+
expect(mutex.locked?).to(eq(true))
|
|
136
143
|
end
|
|
137
144
|
end
|
|
138
|
-
context
|
|
145
|
+
context "changed state" do
|
|
139
146
|
let(:mutex) { Mutex.new }
|
|
140
147
|
subject { mutex.lock }
|
|
141
|
-
it(
|
|
148
|
+
it("can be tested") do
|
|
142
149
|
# Where you used to have:
|
|
143
150
|
# expect { subject }.to change { mutex.locked? }.from(false).to(true)
|
|
144
|
-
block_is_expected.to
|
|
151
|
+
block_is_expected.to(change { mutex.locked? }.from(false).to(true))
|
|
145
152
|
end
|
|
146
153
|
end
|
|
147
154
|
end
|
|
148
155
|
```
|
|
149
156
|
|
|
157
|
+
## Switcch to `main` branch
|
|
158
|
+
|
|
159
|
+
We recently migrated from `master` to `main` as the default branch. If this affected your local checkout:
|
|
160
|
+
```shell
|
|
161
|
+
git branch -m master main
|
|
162
|
+
git fetch origin
|
|
163
|
+
git branch -u origin/main main
|
|
164
|
+
git remote set-head origin -a
|
|
165
|
+
```
|
|
166
|
+
|
|
150
167
|
## Development
|
|
151
168
|
|
|
152
169
|
After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
|
|
@@ -155,26 +172,21 @@ To install this gem onto your local machine, run `bundle exec rake install`. To
|
|
|
155
172
|
|
|
156
173
|
## Authors
|
|
157
174
|
|
|
158
|
-
[Peter H. Boling][peterboling] of [Rails Bling][railsbling] is the author.
|
|
175
|
+
* [Peter H. Boling][peterboling] of [Rails Bling][railsbling] is the author.
|
|
159
176
|
|
|
160
|
-
##
|
|
177
|
+
## Contributing
|
|
161
178
|
|
|
162
|
-
See
|
|
179
|
+
See [CONTRIBUTING.md][contributing].
|
|
180
|
+
[contributing]: https://gitlab.com/pboling/rspec-block_is_expected/-/blob/main/CONTRIBUTING.md
|
|
163
181
|
|
|
164
182
|
## Contributing
|
|
165
183
|
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
3. Commit your changes (`git commit -am 'Added some feature'`)
|
|
169
|
-
4. Push to the branch (`git push origin my-new-feature`)
|
|
170
|
-
5. Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
|
|
171
|
-
6. Create new Pull Request
|
|
172
|
-
|
|
173
|
-
Bug reports and pull requests are welcome on GitHub at https://github.com/pboling/anonymous_active_record. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
|
|
184
|
+
See [CONTRIBUTING.md][contributing].
|
|
185
|
+
[contributing]: https://gitlab.com/pboling/rspec-stubbed_env/-/blob/main/CONTRIBUTING.md
|
|
174
186
|
|
|
175
187
|
## Code of Conduct
|
|
176
188
|
|
|
177
|
-
Everyone interacting in the AnonymousActiveRecord project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct]
|
|
189
|
+
Everyone interacting in the AnonymousActiveRecord project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct][conduct].
|
|
178
190
|
|
|
179
191
|
## Versioning
|
|
180
192
|
|
|
@@ -190,7 +202,7 @@ dependency on this gem using the [Pessimistic Version Constraint][pvc] with two
|
|
|
190
202
|
|
|
191
203
|
For example in a `Gemfile`:
|
|
192
204
|
|
|
193
|
-
gem 'rspec-block_is_expected', '~> 1.0', group: :test
|
|
205
|
+
gem 'rspec-block_is_expected', '~> 1.0', group: [:development, :test]
|
|
194
206
|
|
|
195
207
|
or in a `gemspec`
|
|
196
208
|
|
|
@@ -198,21 +210,31 @@ or in a `gemspec`
|
|
|
198
210
|
|
|
199
211
|
## Legal
|
|
200
212
|
|
|
201
|
-
*
|
|
213
|
+
* Copyright © 2018, 2020, 2023 [Peter H. Boling][peterboling] of [Rails Bling][railsbling]
|
|
202
214
|
|
|
203
|
-
|
|
215
|
+
[](https://opensource.org/licenses/MIT)
|
|
204
216
|
|
|
205
|
-
[
|
|
206
|
-
[
|
|
217
|
+
[aboutme]: https://about.me/peter.boling
|
|
218
|
+
[angellist]: https://angel.co/peter-boling
|
|
219
|
+
[blogpage]: http://www.railsbling.com/tags/rspec-block_is_expected/
|
|
220
|
+
[cc-cov]: https://codeclimate.com/github/pboling/rspec-block_is_expected/test_coverage
|
|
221
|
+
[cc-covi]: https://api.codeclimate.com/v1/badges/ca0a12604ecc19f5e76d/test_coverage
|
|
222
|
+
[conduct]: CODE_OF_CONDUCT.md
|
|
223
|
+
[contributing]: CONTRIBUTING.md
|
|
224
|
+
[depfu]: https://depfu.com/github/pboling/rspec-block_is_expected?project_id=5614
|
|
225
|
+
[depfu-img]: https://badges.depfu.com/badges/272ce0df3bc6df5cbea9354e2c3b65af/count.svg
|
|
226
|
+
[devto]: https://dev.to/galtzo
|
|
207
227
|
[documentation]: http://rdoc.info/github/pboling/rspec-block_is_expected/frames
|
|
228
|
+
[followme]: https://img.shields.io/twitter/follow/galtzo.svg?style=social&label=Follow
|
|
208
229
|
[homepage]: https://github.com/pboling/rspec-block_is_expected
|
|
209
|
-
[
|
|
210
|
-
[license]: LICENSE
|
|
211
|
-
[railsbling]: http://www.railsbling.com
|
|
230
|
+
[license]: LICENSE.txt
|
|
212
231
|
[peterboling]: https://about.me/peter.boling
|
|
213
|
-
[
|
|
214
|
-
[
|
|
215
|
-
[
|
|
216
|
-
[angellist]: https://angel.co/peter-boling
|
|
217
|
-
[coderwall]: http://coderwall.com/pboling
|
|
232
|
+
[pvc]: http://guides.rubygems.org/patterns/#pessimistic-version-constraint
|
|
233
|
+
[railsbling]: http://www.railsbling.com
|
|
234
|
+
[semver]: http://semver.org/
|
|
218
235
|
[twitter]: http://twitter.com/galtzo
|
|
236
|
+
[🧊berg]: https://codeberg.org/pboling
|
|
237
|
+
[🛖hut]: https://sr.ht/~galtzo/
|
|
238
|
+
[🧪lab]: https://gitlab.com/pboling
|
|
239
|
+
[⛳liberapay]: https://liberapay.com/pboling/donate
|
|
240
|
+
[⛳liberapay-img]: https://img.shields.io/liberapay/goal/pboling.svg?logo=liberapay
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
RSpec::Matchers.define_negated_matcher
|
|
2
|
-
RSpec::Matchers.define_negated_matcher
|
|
3
|
-
RSpec::Matchers.define_negated_matcher
|
|
4
|
-
RSpec::Matchers.define_negated_matcher
|
|
1
|
+
RSpec::Matchers.define_negated_matcher(:not_change, :change)
|
|
2
|
+
RSpec::Matchers.define_negated_matcher(:not_include, :include)
|
|
3
|
+
RSpec::Matchers.define_negated_matcher(:not_eq, :eq)
|
|
4
|
+
RSpec::Matchers.define_negated_matcher(:not_raise_error, :raise_error)
|
data.tar.gz.sig
ADDED
|
@@ -0,0 +1 @@
|
|
|
1
|
+
�95mh�q]���k�ݝs==Qth�t�E��p�[���pȱ�2�Ǚ)2���`�YA��xT��O.�Ae��y�U]Kc9�e���N�z |��l����6��)��C�)F���}A/Q9�{(�C�/���x����-�At(R���� '�Z^T��xF���H�W��K�88h1@��}�� �r�{����{�j�JYg�z�e�ue�`&�y:��-ĕT�W٭�Ȕ �5 ��4�t��issUymGc=z)SL��o�~{g� �\\�@E���AjM�i�βX�,��mq�6���Ϝ�����WL����6 �<5�J4zp��=B"������u)b�5ء�A|�tC9W��E�K趋�6䤥c5w���ğ�x% �k1�
|