Unfortunately, the only way to involve developers, in my personal
opinion is to have ATDD as an extension to TDD. A very good reference
is http://specificationbyexample.com/ book.
And man i love this post :)
http://watirmelon.com/2012/01/31/introducing-the-software-testing-ice-cream-cone/
To be
@George,
In my last job Watir was used a lot. The developers on the GUI preferred to
use java-based webdriver. In my current job, I was using a Ruby/Mechanize
class file that some developers used because they could interact with it
(in IRB).
If you think they won't embrace it, you should find
Not yet, but I think they're going to try too. I'm training our QA on watir
and invited the developers as optional participants. A couple of them saw
it as a good way to write unit tests to test client side (jquery, ajax,
javascript) code that won't be covered by their unitest framework. It's a
