Sure, I'll fix that in the next release :)
I didn't followed that approach, matchers (like in RSpec) returns a boolean (or a promise of a boolean value). Errors raised in a matcher will be catched and, as in RSpec, will flag the test as errored (and not as…
I can't completely agree with both of you regarding assertions. There's always cases where a test needs to be done on several properties of an object at once (validation of a rails model attribute, for instance, when…
I'm not really familiar with mocha but you can find a quick comparison with jasmine in my answer here : https://news.ycombinator.com/item?id=6057056
Thanks for the report, I'll look at this as soon I get back home :)
I must say that I'm also a user and lover of jasmine, all the previous lib I did was tested using Jasmine. However, I was missing some feature from RSpec (Jasmine, like Mocha, takes a big part of their syntax from…
Sure, I'll fix that in the next release :)
I didn't followed that approach, matchers (like in RSpec) returns a boolean (or a promise of a boolean value). Errors raised in a matcher will be catched and, as in RSpec, will flag the test as errored (and not as…
I can't completely agree with both of you regarding assertions. There's always cases where a test needs to be done on several properties of an object at once (validation of a rails model attribute, for instance, when…
I'm not really familiar with mocha but you can find a quick comparison with jasmine in my answer here : https://news.ycombinator.com/item?id=6057056
Thanks for the report, I'll look at this as soon I get back home :)
I must say that I'm also a user and lover of jasmine, all the previous lib I did was tested using Jasmine. However, I was missing some feature from RSpec (Jasmine, like Mocha, takes a big part of their syntax from…