Personaly, I only create only the scenario when everything is ok (the
happy path). For controllers, models, etc... I test everything.
Acceptances specs are slow. Test everything in acceptances specs will
make your test suite very very very slow and I think it's useless.
It's only my opinion. So
guirec c. wrote in post #1099350:
> I think your are confused with acceptance specs and controllers spec. In
> a controller spec you must to test only your controller in total
> isolation. You can use stubs and mocks to do it. In the acceptance spec
> you must to test all the behaviour at a very hi
I think your are confused with acceptance specs and controllers spec. In
a controller spec you must to test only your controller in total
isolation. You can use stubs and mocks to do it. In the acceptance spec
you must to test all the behaviour at a very high level.
I think to create a record i
I am building an Rails application where the forgot password feature is
implemented. I need to write the test cases for it using RSpec. I am
very new to RSPEC and got the basic idea of how rspec works from the
tutorial and screencasts. But I am not sure how it can be tested for
controllers. In my c
