rspec-block_is_expected 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: fe189e9ec375dbb1aead1f385e216367faa2d022e2d708a207c3e0e55b3c234f
+  data.tar.gz: 9b49603f4101f1b5543dc511a8d07ebcd3828a75135e02b21f0eb71cf9fc6d20
+SHA512:
+  metadata.gz: 827380bda808ac6e4a4396b83bc8a671fd3fc485e429b3eb4dfb84de1321705ed0a9004eec92a1ba873f1b4f4819733e80c52b290036afa500d2da1e82f318e6
+  data.tar.gz: f98709f7bac689c3ab9c2368e9bbda0da18adc8d1a17b115666e649aa4f62022b7e97bcf00d63318c982520e620f3080f20c974c067100a10464d1491b7e3e3d

data/.gitignore

@@ -0,0 +1,13 @@
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/*.gem
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+
+# rspec failure tracking
+.rspec_status

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,35 @@
+AllCops:
+  DisplayCopNames: true # Display the name of the failing cops
+  Exclude:
+    - 'gemfiles/vendor/**/*'
+    - 'vendor/**/*'
+
+Metrics/BlockLength:
+  ExcludedMethods:
+    - context
+    - describe
+    - it
+    - shared_context
+    - shared_examples
+    - shared_examples_for
+    - namespace
+    - draw
+
+Metrics/LineLength:
+  Enabled: false
+
+Style/HashSyntax:
+  EnforcedStyle: hash_rockets
+
+Style/Lambda:
+  Enabled: false
+
+Style/PercentLiteralDelimiters:
+  Enabled: false
+
+Style/SymbolArray:
+  Enabled: false
+
+# Enable when drop support for Ruby < 2
+Style/ExpandPathArguments:
+  Enabled: false

data/.travis.yml

@@ -0,0 +1,61 @@
+env:
+  global:
+  - JRUBY_OPTS="-Xcli.debug=true --debug"
+  - CC_TEST_REPORTER_ID=13484ad644dba9dd92ac41ef387f76b3c24d73a668ed4d044c933ec14943257d
+
+before_script:
+- curl -L https://codeclimate.com/downloads/test-reporter/test-reporter-latest-linux-amd64 > ./cc-test-reporter
+- chmod +x ./cc-test-reporter
+- ./cc-test-reporter before-build
+
+script:
+- bundle exec rspec
+
+after_script:
+- ./cc-test-reporter after-build --exit-code $TRAVIS_TEST_RESULT
+
+before_install:
+- gem update --system
+- gem install bundler
+
+install:
+- bundle install
+
+bundler_args: --no-deployment --jobs 3 --retry 3
+
+cache: bundler
+
+language: ruby
+sudo: false
+matrix:
+  allow_failures:
+  - rvm: jruby-head
+  - rvm: ruby-head
+  fast_finish: true
+  include:
+  - rvm: 1.8.7-p371
+    gemfile: gemfiles/ruby_1.8.7_p371.gemfile
+  - rvm: 1.9.3-p551
+    gemfile: gemfiles/ruby_1.9.3_p551.gemfile
+  - rvm: 2.0.0-p648
+    gemfile: gemfiles/ruby_2.0.0_p648.gemfile
+  - rvm: 2.1.10
+    gemfile: gemfiles/ruby_2.1.10.gemfile
+  - rvm: 2.2.10
+    gemfile: gemfiles/ruby_2.2.10.gemfile
+  - rvm: 2.3.7
+    gemfile: gemfiles/ruby_2.3.7.gemfile
+  - rvm: 2.4.4
+    gemfile: gemfiles/ruby_2.4.4.gemfile
+  - rvm: 2.5.1
+    gemfile: gemfiles/ruby_2.5.1.gemfile
+  - rvm: ruby-head
+    gemfile: gemfiles/ruby_head.gemfile
+  - rvm: jruby-1.7.26
+    gemfile: gemfiles/jruby_1.7.26.gemfile
+  - rvm: jruby-9.1.9.0
+    gemfile: gemfiles/jruby_9.1.9.0.gemfile
+  - rvm: jruby-9.2.0.0
+    gemfile: gemfiles/jruby_9.2.0.0.gemfile
+  - rvm: jruby-head
+    gemfile: gemfiles/jruby_head.gemfile

data/Appraisals

@@ -0,0 +1,32 @@
+appraise 'jruby-1.7.26' do
+end
+
+appraise 'ruby-1.8.7-p371' do
+end
+
+appraise 'ruby-1.9.3-p551' do
+end
+
+appraise 'ruby-2.0.0-p648' do
+end
+
+appraise 'ruby-2.1.10' do
+end
+
+appraise 'ruby-2.2.10' do
+end
+
+appraise 'jruby-9.1.9.0' do
+end
+
+appraise 'ruby-2.3.7' do
+end
+
+appraise 'ruby-2.4.4' do
+end
+
+appraise 'ruby-2.5.1' do
+end
+
+appraise 'jruby-9.2.0.0' do
+end

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at peter.boling@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,20 @@
+source 'https://rubygems.org'
+
+git_source(:github) { |repo_name| "https://github.com/#{repo_name}" }
+
+group :test do
+  ruby_version = Gem::Version.new(RUBY_VERSION)
+  if ruby_version >= Gem::Version.new('2.1')
+    gem 'rubocop', '~> 0.59.0'
+    gem 'rubocop-rspec', '~> 1.24.0'
+  end
+  if ruby_version >= Gem::Version.new('2.0')
+    gem 'byebug', '~> 10', platform: :mri, require: false
+    gem 'pry', '~> 0', platform: :mri, require: false
+    gem 'pry-byebug', '~> 3', platform: :mri, require: false
+  end
+  gem 'simplecov', '~> 0', require: false
+end
+
+# Specify your gem's dependencies in rspec-block_is_expected.gemspec
+gemspec

data/LICENSE

@@ -0,0 +1,22 @@
+Copyright (c) 2018 Peter H. Boling of RailsBling.com
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,157 @@
+# Rspec::BlockIsExpected
+
+This gem does one very simple thing very well.  It allows you to use `block_is_expected` similarly to how you would use `is_expected` if a block was wrapping the subject.  Supports the same versions of Ruby that RSpec does, 1.8.7 - current ruby-head, as well as the JRuby equivalents.
+
+```ruby
+subject { Integer(nil) }
+it('raises') { block_is_expected.to raise_error(TypeError) }
+```
+
+| Project                 |  AnonymousActiveRecord |
+|------------------------ | ----------------------- |
+| gem name                |  [rspec-block_is_expected](https://rubygems.org/gems/rspec-block_is_expected) |
+| license                 |  [![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) |
+| download rank           |  [![Downloads Today](https://img.shields.io/gem/rd/rspec-block_is_expected.svg)](https://github.com/pboling/rspec-block_is_expected) |
+| version                 |  [![Version](https://img.shields.io/gem/v/rspec-block_is_expected.svg)](https://rubygems.org/gems/rspec-block_is_expected) |
+| dependencies            |  [![Depfu](https://badges.depfu.com/badges/272ce0df3bc6df5cbea9354e2c3b65af/count.svg)](https://depfu.com/github/pboling/rspec-block_is_expected?project_id=5614) |
+| continuous integration  |  [![Build Status](https://travis-ci.org/pboling/rspec-block_is_expected.svg?branch=master)](https://travis-ci.org/pboling/rspec-block_is_expected) |
+| test coverage           |  [![Test Coverage](https://api.codeclimate.com/v1/badges/ca0a12604ecc19f5e76d/test_coverage)](https://codeclimate.com/github/pboling/rspec-block_is_expected/test_coverage) |
+| maintainability         |  [![Maintainability](https://api.codeclimate.com/v1/badges/ca0a12604ecc19f5e76d/maintainability)](https://codeclimate.com/github/pboling/rspec-block_is_expected/maintainability) |
+| code triage             |  [![Open Source Helpers](https://www.codetriage.com/pboling/rspec-block_is_expected/badges/users.svg)](https://www.codetriage.com/pboling/rspec-block_is_expected) |
+| homepage                |  [on Github.com][homepage], [on Railsbling.com][blogpage] |
+| documentation           |  [on RDoc.info][documentation] |
+| Spread ~♡ⓛⓞⓥⓔ♡~      |  [🌍 🌎 🌏][peterboling], [🍚][refugees], [➕][gplus], [👼][angellist], [🐛][topcoder], [:shipit:][coderwall], [![Tweet Peter](https://img.shields.io/twitter/follow/galtzo.svg?style=social&label=Follow)][twitter] |
+
+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/).
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'rspec-block_is_expected', group: :test
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install rspec-block_is_expected
+
+## Configuration
+
+There is no configuration needed if you your test suite loads the bundle group (e.g. `test`) that you added the gem to.
+
+Otherwise, you may load it manually near the top of your `spec_helper.rb`, and it will self configure.
+```ruby
+require 'rspec/block_is_expected'
+```
+
+## Usage
+
+The spec suite for this gem has some examples of usage, lightly edited here.
+
+```ruby
+RSpec.describe 'TestyMcTest' do
+  context 'errors raised' do
+    subject { Integer(nil) }
+    it('can be tested') do
+      # Where you used to have:
+      # expect { subject }.to raise_error(TypeError)
+      block_is_expected.to raise_error(TypeError)
+    end
+  end
+  context 'execution' do
+    let(:mutex) { Mutex.new }
+    subject { mutex.lock }
+    it('can change state') do
+      expect(mutex.locked?).to eq(false)
+      # Where you used to have:
+      # expect { subject }.to_not raise_error
+      block_is_expected.to_not raise_error
+      expect(mutex.locked?).to eq(true)
+    end
+  end
+  context 'changed state' do
+    let(:mutex) { Mutex.new }
+    subject { mutex.lock }
+    it('can be tested') do
+      # Where you used to have:
+      # expect { subject }.to change { mutex.locked? }.from(false).to(true)
+      block_is_expected.to change { mutex.locked? }.from(false).to(true)
+    end
+  end
+end
+```
+
+## Development
+
+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.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then 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](https://rubygems.org).
+
+## Authors
+
+[Peter H. Boling][peterboling] of [Rails Bling][railsbling] is the author.
+
+## Contributors
+
+See the [Network View](https://github.com/pboling/rspec-block_is_expected/network) and the [CHANGELOG](https://github.com/pboling/rspec-block_is_expected/blob/master/CHANGELOG.md)
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Added some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
+6. Create new Pull Request
+
+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.
+
+## Code of Conduct
+
+Everyone interacting in the AnonymousActiveRecord project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/pboling/anonymous_active_record/blob/master/CODE_OF_CONDUCT.md).
+
+## Versioning
+
+This library aims to adhere to [Semantic Versioning 2.0.0][semver].
+Violations of this scheme should be reported as bugs. Specifically,
+if a minor or patch version is released that breaks backward
+compatibility, a new version should be immediately released that
+restores compatibility. Breaking changes to the public API will
+only be introduced with new major versions.
+
+As a result of this policy, you can (and should) specify a
+dependency on this gem using the [Pessimistic Version Constraint][pvc] with two digits of precision.
+
+For example in a `Gemfile`:
+
+    gem 'rspec-block_is_expected', '~> 1.0', group: :test
+
+or in a `gemspec`
+
+    spec.add_development_dependency 'rspec-block_is_expected', '~> 1.0'
+
+## Legal
+
+* MIT License - See [LICENSE][license] file in this project [![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT) 
+
+* Copyright (c) 2018 [Peter H. Boling][peterboling] of [Rails Bling][railsbling]
+
+[semver]: http://semver.org/
+[pvc]: http://guides.rubygems.org/patterns/#pessimistic-version-constraint
+[documentation]: http://rdoc.info/github/pboling/rspec-block_is_expected/frames
+[homepage]: https://github.com/pboling/rspec-block_is_expected
+[blogpage]: http://www.railsbling.com/tags/rspec-block_is_expected/
+[license]: LICENSE
+[railsbling]: http://www.railsbling.com
+[peterboling]: https://about.me/peter.boling
+[refugees]: https://www.crowdrise.com/helprefugeeswithhopefortomorrowliberia/fundraiser/peterboling
+[gplus]: https://plus.google.com/+PeterBoling/posts
+[topcoder]: https://www.topcoder.com/members/pboling/
+[angellist]: https://angel.co/peter-boling
+[coderwall]: http://coderwall.com/pboling
+[twitter]: http://twitter.com/galtzo

data/Rakefile

@@ -0,0 +1,28 @@
+require 'bundler/gem_tasks'
+begin
+  require 'wwtd/tasks'
+rescue LoadError
+  puts 'failed to load wwtd'
+end
+
+begin
+  require 'rspec/core/rake_task'
+  RSpec::Core::RakeTask.new(:spec)
+rescue LoadError
+  # puts "failed to load wwtd or rspec, probably because bundled --without-development"
+  task :spec do
+    warn 'rspec is disabled'
+  end
+end
+task :test => :spec
+
+begin
+  require 'rubocop/rake_task'
+  RuboCop::RakeTask.new
+rescue LoadError
+  task :rubocop do
+    warn 'RuboCop is disabled'
+  end
+end
+
+task :default => [:test, :rubocop]