Comments on Andrzej on Software: Object oriented acceptance testing

@Jo Yes, I also prefer to have the steps calls in...

2011-04-11T19:03:31.369+02:00

@Jo

Yes, I also prefer to have the steps calls in Ruby.

You're right, having it as #see would be the RSpec-way. Thanks. I'm still not sure if going with the Steak/Rspec combination is the best way. Next project I'm starting with Capybara + minitest and see if it's easier without RSpec magic.

I like your TestUser class -- I think it's a g...

2011-04-11T18:48:19.682+02:00

I like your TestUser class -- I think it's a great way to do Cucumber step definitions in actual Ruby code.

One thing though, perhaps it's better to not have should_ methods, but rather plain predicates. So instead of user.should_see('foo'), I'd suggest doing user.should see('foo'), where TestUser#sees? is a predicate method.

@Seban Thanks! I would not be able to work witho...

2011-04-07T14:25:43.941+02:00

@Seban

Thanks!

I would not be able to work without acceptance tests. Unit tests are important but there is lots of problems that can appear at the integration level.

Feel free to register at http://Plansza24.pl :)

I've never used acceptance tests in real proje...

2011-04-07T08:32:22.956+02:00

I've never used acceptance tests in real project- I don't need to I prefer good old-school unit testing. But your way is nice for me. I think it is better for programmer. Waiting to hear more about yours ideas about acceptance testing.
BTW. I like board games! ;)