rspec-the 0.0.2 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: f7aaaab1b63bd8f5fca9a41b3a4dc201f03c1f3c
-  data.tar.gz: 7e3bc98ffd9e798daf77dc39e1b7183fdebeb99b
+  metadata.gz: 11f700928861f020121522ef2d06c19a4838ea48
+  data.tar.gz: c70a8ac731bbc6d3a34c0adcda2251bed1ee1c3e
 SHA512:
-  metadata.gz: 196a096f17176604691ccaa399effa79660862389e184a3d91a40081fe7ae97aa37c14ec16bd13330d6ccd364c81f29385bb4ce954dfb8211f0dc4db673e79ca
-  data.tar.gz: 6bd858e876647236928e084f6018469035e624f4c5a7d4f88dbf9e5bccd169125b5191a2fedc71d67ed479a7e1a3e2f6107656adccc28ffb1438ba347aca1a78
+  metadata.gz: 115c7ebb055c9aa4b065f36cb9f0a5dcdd8e908919ad785d47b317d7ce521cfea306e939099028486c5899351596bb51de7f191f5c6918d4b2d2399ecf226ad7
+  data.tar.gz: d3079a61ca59b1e2c3ab9cdff215fef91570736fff2526fdd46e4df342a5eb34a1d41dbee5fddab2c7f76209d764273db663d6e6290277bf41ae9016e2af4a91

data/.travis.yml

@@ -0,0 +1,9 @@
+language: ruby
+rvm:
+  - 1.9.3
+  - 2.0
+  - 2.1
+  - 2.2
+script: bundle exec rspec spec
+sudo: false
+cache: bundler

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    rspec-the (0.0.2)
+    rspec-the (1.0.0)
       rspec-core (>= 3.0.0)
       rspec-expectations (>= 3.0.0)
 

data/README.md

@@ -2,6 +2,9 @@
 
 Easily make assertions about the contents of your `let` blocks
 
+[![Travis Status](https://img.shields.io/travis/jamesottaway/rspec-the.svg)](https://travis-ci.org/jamesottaway/rspec-the)
+[![RubyGems Version](https://img.shields.io/gem/v/rspec-the.svg)](https://rubygems.org/gems/rspec-the)
+
 ## Installation
 
 Add this line to your application's Gemfile:
@@ -12,25 +15,63 @@ gem 'rspec-the'
 
 And then execute:
 
-    $ bundle
+```
+bundle install
+```
 
 Or install it yourself as:
 
-    $ gem install rspec-the
+```
+gem install rspec-the
+```
 
 ## Usage
 
-```ruby
-describe 'something' do
-  let(:value) { 42 }
-  the(:value) { is_expected.to eq 42 }
+Using `rspec-its` to test your given `subject` works for simple method invocations, but requires excessive nesting in more complex scenarios.
+
+``` ruby
+describe Array do
+  let(:array) { [1, 2, 3, 4, 5] }
+  subject { array }
+
+  its(:count) { is_expected.to eq 5 }
+  its(:first) { is_expected.to eq 1 }
+
+  describe 'select #even?' do
+    subject { array.select(&:even?) }
+    it { is_expected.to eq [2, 4] }
+  end
+
+  describe 'select #odd?' do
+    subject { array.select(&:odd?) }
+    it { is_expected.to eq [1, 3, 5] }
+  end
 end
 ```
 
+Instead, `rspec-the` allows us use `let` to define many pseudo-`subject` blocks which can easily be tested.
+
+``` ruby
+describe Array do
+  subject { [1, 2, 3, 4, 5] }
+
+  its(:count) { is_expected.to eq 5 }
+  its(:first) { is_expected.to eq 1 }
+
+  let(:evens) { subject.select(&:even?) }
+  the(:evens) { is_expected.to eq [2, 4] }
+
+  let(:odds) { subject.select(&:odd?) }
+  the(:odds) { is_expected.to eq [1, 3, 5] }
+end
+```
+
+See, isn't that easier?!?
+
 ## Contributing
 
 1. Fork it ( https://github.com/jamesottaway/rspec-the/fork )
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create a new Pull Request
+2. Create your feature branch (`git checkout -b $BRANCH_NAME`)
+3. Commit your changes (`git commit --all --message $COMMIT_MESSAGE`)
+4. Push to the branch (`git push $REMOTE $BRANCH_NAME`)
+5. Create a new Pull Request ( https://github.com/jamesottaway/rspec-the/compare )

data/rspec-the.gemspec

@@ -4,7 +4,7 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 
 Gem::Specification.new do |spec|
   spec.name          = 'rspec-the'
-  spec.version       = '0.0.2'
+  spec.version       = '1.0.0'
   spec.authors       = ['James Ottaway']
   spec.email         = ['hello@james.ottaway.io']
   spec.summary       = 'Easily make assertions about the contents of your `let` blocks'

data/spec/rspec/the_spec.rb

@@ -1,5 +1,5 @@
 require 'rspec/the'
-require 'counter'
+require 'spec_helper'
 
 describe RSpec::The do
   describe '#the' do
@@ -14,7 +14,7 @@ describe RSpec::The do
     context '#are_expected' do
       let(:counter) { Counter.new }
       before { expect(counter.next).to eq 1 }
-      let(:nexts) { 5.times.inject([]) { |acc| acc << counter.next } }
+      let(:nexts) { 5.times.inject [] { |acc| acc << counter.next } }
       the(:nexts) { are_expected.to eq [2, 3, 4, 5, 6] }
       after { expect(counter.next).to eq 7 }
     end

data/spec/spec_helper.rb

@@ -0,0 +1,5 @@
+Dir.chdir 'spec' do
+  Dir.glob('support/**/*.rb').each do |file|
+    require file
+  end
+end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rspec-the
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 1.0.0
 platform: ruby
 authors:
 - James Ottaway
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-12-16 00:00:00.000000000 Z
+date: 2014-12-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec-core
@@ -75,6 +75,7 @@ extra_rdoc_files: []
 files:
 - ".gitignore"
 - ".ruby-version"
+- ".travis.yml"
 - Gemfile
 - Gemfile.lock
 - LICENSE.txt
@@ -82,8 +83,9 @@ files:
 - Rakefile
 - lib/rspec/the.rb
 - rspec-the.gemspec
-- spec/counter.rb
 - spec/rspec/the_spec.rb
+- spec/spec_helper.rb
+- spec/support/counter.rb
 homepage: https://github.com/jamesottaway/rspec-the
 licenses:
 - MIT
@@ -109,5 +111,6 @@ signing_key:
 specification_version: 4
 summary: Easily make assertions about the contents of your `let` blocks
 test_files:
-- spec/counter.rb
 - spec/rspec/the_spec.rb
+- spec/spec_helper.rb
+- spec/support/counter.rb