Skip to content
This repository has been archived by the owner on May 8, 2018. It is now read-only.

rspec and shoulda? #5

Closed
NobbZ opened this issue Aug 11, 2011 · 4 comments
Closed

rspec and shoulda? #5

NobbZ opened this issue Aug 11, 2011 · 4 comments

Comments

@NobbZ
Copy link
Contributor

NobbZ commented Aug 11, 2011

Why are there rspec and shoulda in the Gemfile?

So far as I can tell both are used for the same purpose, they are both a replacement for unit tests, or do I missunderstand things?

Additionally it seems that shoulda is not really used in the tests, so can we remove it safely?

@NobbZ
Copy link
Contributor Author

NobbZ commented Aug 11, 2011

Also I think a cleanup of features, specs or/and tests is quite necessary. I think this cleanup fits very well into the fact that there are two testing frameworks required in the Gemfile...

@epitron
Copy link
Collaborator

epitron commented Aug 11, 2011

Agreed. I just committed what I was working on yesterday -- removing extraneous things from the Gemfile.

The tests are out of date in other ways too -- Factory Girl deprecated the use of the 'Factory' module.

Nothing complicated... just a little maintenance work. :)

@locriani
Copy link
Owner

Shoulda extends RSpec functionality, it's not a separate test / test harness framework.

Sent from my iPhone

On Aug 11, 2011, at 3:31, NobbZreply@reply.github.com wrote:

Why are there rspec and shoulda in the Gemfile?

So far as I can tell both are used for the same purpose, they are both a replacement for unit tests, or do I missunderstand things?

Additionally it seems that shoulda is not really used in the tests, so can we remove it safely?

Reply to this email directly or view it on GitHub:
#5

@epitron
Copy link
Collaborator

epitron commented Aug 11, 2011

Whoops, sorry. I was confusing it with bacon or something.

@epitron epitron closed this as completed Aug 12, 2011
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants