Use RSpec as default test framework

[sheerun]

Evaluated Alternatives

Rspec, Minitest, Test::Unit, Bacon, Riot, and less popular

Reasoning

• It seems to be most popular Test Framework
• It comes with lot of integrations, including editors like vim (Bacon)
• BDD-like commands put you in different mindset (Riot, Test-Unit)
• Easy controller tests work out of the box (Minitest)
• Developers already know how to use it (less popular)
• Advanced support for mocks and stubs (Test::Unit, Bacon, Riot)
• In my experience RSpec comparing to Minitest doesn't require many configuration, and much gems have simple integration implemented.

  Acknowledged downsides

• Unit Tests can run slower than in other frameworks. To prevent this you should try to isolate your tests.
• Weird matchers (42.should eq(42)). The solution is to use wrong plugin, which allows you to write verbose tests like assert { 42 == 42 }.

[teamon]

I would argue with "doesn't require many configuration". RSpec for rails, minitest for others.

[sheerun]

"much configuration" of course

[jandudulski]

Weird matchers (42.should eq(42))

There is a new syntax and you should start using it now:

expect(42).to eq(42)

But I agree recommending rspec for rails and minitest for others.

[sheerun]

I don't see such guideline ;)

On Mon, Aug 5, 2013 at 12:19 PM, Jan Dudulski notifications@github.comwrote:

Weird matchers (42.should eq(42))

There is a new syntax and you should start using it now:

expect(42).to eq(42)

But I agree recommending rspec for rails and minitest for others.

— Reply to this email directly or view it on GitHubhttps://github.com/monterail/guidelines/issues/163#issuecomment-22097583 .

[jandudulski]

I don't see such guideline ;)

You're welcome #170 ;)