Some rely on other harnesses like xUnit and provide mechanisms for faking mouse and
keyboard input, similar to the way the commercial WinRunner?„? tool interfaces with TestDirector?„?
(now Quality Center). Only choose an open source GUI tool which supports object-based automation.
Then check how many of your objects it
can??™t
???see.???
7.4.9 About GUI Testing
Early GUI test tools were ???analog??? in that that they recorded mouse movements using X-Y screen
coordinates alone. Analog capture and replay of test scripts requires much maintenance to the extent of
rewriting all the test scripts whenever there is a change to the GUI. Analog scripts may also be sensitive
to changes in screen resolution, color depth, and where the window is placed on the screen.
Later GUI test tools were object-based and recognized many of the objects in a graphical application,
like buttons, menus, and text input widgets, and referred to them symbolically rather than by screen
coordinates. This technique was more resilient to changes in the GUI design, screen resolution, etc.,
though the tests still needed to be changed if a GUI control changes; additionally some controls were
often not recognized if the developers used custom-developed controls or a toolkit that the tool cannot
understand. Object-based tools can also use style-style screen coordinates if necessary.
A newer idea is ???keyword-driven??? testing in which test data is specified as with data-driven testing,
but which also uses pre-defined keywords to define actions for a test case to take.
Pages:
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264