Chapter 17. Organizing Acceptance Tests


We've almost reached the end of the second day of our trip. The road's still pretty flat, but in the distance we can see the mountains we'll have to scale later in the iteration. The last stretch of today's road leaves us on the outskirts of test automation, where we'll start in the morning. Up to this point, we've been concerned primarily with what to test: which stories, what scenarios, which details, what inputs, what expected results, and so on. Now our attention is turning more to how to test these things.

We've already written some executable tests, and before we quit for the day, we'll take a look at how to keep them organized. There could be a fair number of them, and you and everyone on the team need to be able to call up the latest version of any test to run and/or refactor. The customer, meanwhile, may require a modified format if he can't work with the executable tests directly, and the two versions need to be kept in sync.



Testing Extreme Programming
Testing Extreme Programming
ISBN: 0321113551
EAN: 2147483647
Year: 2005
Pages: 238

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net