Chapter 24. Driving the System with a Test Tool


In the previous chapter, we illustrated how to make the executable tests run through other interfaces besides direct calls to the code. Without making any changes to the XTrack tests themselves, we added a few lower-level classes to send the tests to the WebART tool, to be played through the XTrack browser interface. When we finished, we were able to send the tests to WebART, but the tests all failed, because we hadn't done anything in WebART to perform the tests. In this chapter, we're going to complete the process by doing exactly that.

The details of how this is done are, of course, highly tool-specific, so we're not going to get overly detailed. Our goal is not to make you expert (or even proficient) at using this particular tool but to prove by example that it's possible. We'll use the example to discuss validation issues that always come up when automating tests at or near the user interface, regardless of the tool used. You can apply this to whatever tool seems suitable to your project. See Chapter 29 for more about developing and selecting test tools.

We won't pretend this is easy to grasp upon first read. We recommend that you try working through the exercise for this chapter. Stick it out it's not as bad as it looks. You might feel you're teetering on the edge of a cliff right now, but we have plenty of safety gear!



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