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 on topic, i didn't managed to convinced them. On Feb 7, 9:55 pm, George <george.sand...@gmail.com> wrote: > Hi there, > > My company is determining a solid automation framework that will be > used by both QA and developers. Although I've created a ton of Watir > scripts, I'm pretty sure that the developers will not embrace will > I've put together. Has anyone had any success in convincing your > developers to use Watir? > > -George -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com
