AUTOMATED INTEGRATION TESTING in Font

Maker USS Code 39 in Font AUTOMATED INTEGRATION TESTING

every line should be followed by a Then that shows how the system responded, and allows the test to confirm that this actually happened. To generate a DDT-equivalent BDD scenario, each When step would be immediately followed by a counterpart Then system response. So the example BDD scenario, written in a more DDT-like style, would read as follows:

Given the system displays the Map Viewer And an AOI exists of local size Then the system enables the Advanced Search widget When the user clicks the Advanced Search icon Then the system expands the Advanced Search widget and populates fields with defaults When the user specifies Reservation Details of check-in today and check-out next week, 2 adults and 1 room Then the system checks that the dates are valid When the user selects Hotel Filter criteria And the user clicks FIND Then the system displays the Hotels on the map and List Widget

It should then be a relatively straightforward task to map each test case to a specific BDD step. At the time of writing, there s a paucity of BDD support for Flex developers. So we ll show the example here using the Java-based JBehave (which also happens to leverage JUnit, meaning that your JBehave-based scenario tests can be run on any build/test server that supports running JUnit tests).

Note ICONIX-style active voice use cases often start with a screen being displayed. So we changed the opening part of the scenario to begin with displaying the Map Viewer. This results in a check being performed to verify that the system properly displays the Advanced Search widget.

Testing GUI code is often shied away from as the most apparently difficult part of automated testing. In the past, it certainly used to be, with heavyweight robot -style frameworks simulating mouse clicks at rigid X,Y screen co-ordinates. Naturally such frameworks were ridiculously fragile, as even a change in screen resolution or window decoration (anything that even slightly offsets the X, Y co-ordinates) would break the entire suite of tests and require every single test to be redone.

GUI testing has come a long way in recent times, though. Swing developers have it easy with toolkits such as Abbot,7 UISpec4J,8 and FEST.9 Swing testing is actually pretty straightforward even without an additional toolkit, as everything s accessible via the code, and with built-in methods already available such as button.doClick(). .NET developers may like to check out NunitForms,10 an NUnit extension for windows.forms testing. Flex developers also have plenty of options, e.g., FlexMonkey11 and RIATest.12 And finally, web developers are probably already familiar with the deservedly popular Selenium web testing framework.13 The ever-changing nature of web development where the delivery platform of the month is usually specific versions of half a dozen different web browsers, and IE 6, but next month could involve a whole new set of browser versions means that automated scenario testing is more important than ever for web developers. Swapping a different browser version into your tests provides a good early indication of whether a browser update will cause problems for your application.

Integration tests can be problematic. Don t underestimate by how much. Unit testing testing in the small is really about matching up the interface between the calling code and the function being tested. Interfaces are inherently tricky, because they can change. So what happens if you zoom out from this close-in picture, and start to look at remote interfaces It s easy (and rather common) to picture a remote systems environment like the one in Figure 11 3. Client code makes a call out over the network to a remote interface, retrieves the result, and (in the case of a test) asserts that the result is as expected. Unfortunately, the reality is more like Figure 11 4.

7 8 9

http://abbot.sourceforge.net/doc/overview.shtml www.uispec4j.org http://fest.easytesting.org/swing/wiki/pmwiki.php http://nunitforms.sourceforge.net/ www.gorillalogic.com/flexmonkey www.riatest.com http://seleniumhq.org/

10 11 12 13