Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

I insist. (a testing tool for ruby)

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 .batcave
Octocat-spinner-32 lib
Octocat-spinner-32 spec
Octocat-spinner-32 test
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .travis.yml
Octocat-spinner-32 Gemfile
Octocat-spinner-32 Gemfile.lock
Octocat-spinner-32 LICENSE
Octocat-spinner-32 Makefile
Octocat-spinner-32 README.md
Octocat-spinner-32 insist.gemspec
Octocat-spinner-32 notify-failure.sh
README.md

insist { on readable assertions }

I like rspec, but I don't like the '#should' junk. It scratches me the wrong way, I guess. I find this to be an unreadable mess:

# yuck, if you ask me.
somevalue.should eq(0)

On the flip side, I really like the idea (make tests read like english).

So instead of slapping '#should' on all objects and doing weird stuff like expect { block }.to raise_error(thing), I just use blocks for everything in a kind of lazy-evaluation wrapping:

# Check equality
insist { value } == 30

# Insist an exception is raised
insist { code }.raises(exception_class)

Reads well, I think.

Most minimal assertions possible

Using rspec's 'subject' stuff, you can write tests that are perhaps even more minimal while still being clear.

Here's an example test that fails. The subject is an 'insist' object, so you can just do the usual '==' and other methods on it:

# spec/example_spec.rb
describe "thing" do
  subject { insist { "whoa!" } }

  it "should be, like, awesome!" do
    subject == "awesome!"
  end
end

Running it:

Failures:

  1) thing should be, like, awesome!
     Failure/Error: subject == "awesome!"
     Insist::Failure:
       Expected "awesome!", but got "whoa!"
     # ./lib/insist/assert.rb:8:in `assert'
     # ./lib/insist/comparators.rb:12:in `=='
     # ./test.rb:5:in `block (2 levels) in <top (required)>'

Finished in 0.00208 seconds
1 example, 1 failure

Failed examples:

rspec ./test.rb:4 # thing should be, like, awesome!
Something went wrong with that request. Please try again.