On Sun, Oct 10, 2010 at 1:17 PM, [email protected] <
[email protected]> wrote:
i am having some issues around ruby-debug and rspec for rails3 so i
was doing a google search for a solution and came across this thread.
i’m sorry I couldn’t miss your thoughts on rppec vs cucumber and don’t
wanna play smarty pants here, i just think you cannot replace rppec
with cucumber because they are different tools really for different
I am new to both rspec and cucumber and still feeling my way. But at
for my current app what I am finding is that by starting with Cucumber,
cover the user experience pretty well, then just write specs as I write
models, etc. But the confidence I have in my app is higher and also I am
seeing (so far) that my focus is better. Maybe in a few weeks I can let
know but I am finding that if I have good cucumber coverage I feel less
compulsive about the lower level test coverage and save time and effort
this. Of course, if I am writing a safety critical or highly sensitive
component of course I would throw all the lower level stuff at it too.
some thoughts from where I am currently.
i am also using cucumber for testing my projects’ integrity - hence
cucumber is for integration testing! - but also not lazy to write
specs for my controller tests. i found that writing unit tests with
I did for a bit write controller specs but they got overwhelming and I
decided based on the 80/20 principle to just trust my cucumber results.
Maybe I am wrong… time will tell But I don’t disagree with your
I think it probably goes back to what it is you want to test. I actually
changed my method of handling roles so that I could test the class using
rspec on the model, that made me feel that although I could perhaps find
some problems writing controller specs, it would be diminishing returns.