Activity (RSS)

Many of the matchers could do with strict / non-strict versions similar to eql and equal resulting in assertions like below:

response = { ran : '1' }
respon...

Like below:

a = 1..5
a.inject('', function(memo, v){
  return memo + v
}).should.eql '12345'

Currently the description 'Object' '.foo' will display as 'Object .foo', when starting with a period collapse to 'Object.foo'

Meta-generate have_title 'foo', have_id 'foo' etc with common attributes

Pretty redundant, mise well utilize the have_attr matcher

Only nice feature of screw-unit, however this does not seem very useful to me, would slow things down IMO needing to even manually switch between browsers and c...

indenting the nested specs although this lowers realestate

Add this to the site to allow people to quickly scan feature-sets

All arbitrary exceptions thrown should fail the spec, but should not fail the entire suite

With latest matchers, ranges etc

Leaving for now since its not a huge deal. Easier fix if JS regexps supported negative lookbehinds

So for instance displayFailures : true could be ?displayFailures=1 etc

Use this for this.formatter as well ... document

 foo.should_receive('meth').with(an_instance_of(Array), an_instance_of(String))
foo.should_receive('meth').with('foo').once

chain together the replace calls, and renamed to preprocess

No need to separate these two option hashes, alter README

The following throw a parse error due to the regexps consuming to much data

 ...
 // -{
 // foo.should.equal bar
 ...

will simplify parsing greatly and provide for some more features in the future

double check, make spec

To show how many assertions have failed within the spec block

:D share the love!

lucy.should.have(2).pets