We've just setup Jenkins as CI yesterday, though this isn't the first time we've used it, and it seems to be pretty good. I'm not a fan of plain language specifications myself, though am finding on our current project that rspec syntax in combination with Capybara steps (no cucumber) is very readable. I don't think it's feasible to get a BA to write the acutal tests/specs personally, and if they only need to specify what you're testing, not write it themselves, then sitting down with a BA/tester and writing some specs then is a nice way to go.
On 10 February 2012 11:59, ben.biddington <[email protected]> wrote: > Hi fellows, > > Just wondered what your thoughts are on employing automated acceptance > tests (AAT) for web applications, particularly "rich client" (if > that's the term du jour). > > Anybody writing executable specifications with testers/customers? If > so, have you found plain language specifications useful, or a burden > that nobody ever reads? > > What about CI? How unwieldy are your builds? > > What're you using? Cucumber? Fit? Concordion? > > And if you do have AAT in place, how then are you using your human > testers? > > <bb /> > > -- > You received this message because you are subscribed to the Google Groups > "WellRailed" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/wellrailed?hl=en. > > -- Jeremy Olliver -- You received this message because you are subscribed to the Google Groups "WellRailed" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wellrailed?hl=en.
