Testing games is in many ways similar to testing many complex, multi-media applications. In this hands-on presentation, Hans Buwalda demonstrates practical ways to automatically test a game using an intelligent, model-driven robot. Learn a straightforward technique using action words that you can apply in a wide variety of complex testing situations. The only technology you need to get started is an everyday spreadsheet program such as Microsoft Excel. Find out how combining a simple model of your application with the action word approach can measurably improve your testing.

Not every test automation project should be done and not all deserve the highest priority. You need a repeatable process that you can use to filter requests to automate tests. Find out how to assess effort, impact, likelihood of success to select the right projects for automating. Learn to use risk management techniques to refine the process, and begin assigning criteria and ranking every suggested automation project. With this process in place, you’ll choose the right project to do now and the right one to do next.

Migrating a testing infrastructure from data-driven test automation to a model-driven test architecture, including the need to maintain backward compatibility was a huge challenge for Michael Corning and his groupx0151but a very rewarding one. The test group manages three modeling tools supporting both state-based and grammar-based modeling techniques. Modeling became important and ultimately indispensable not only for product testing but for the test infrastructure development as well. The results can be programs that are self-documenting and virtually self-testing.

GUI-centric automation scripting is a major cause of the high costs and failed test automation efforts. These scripts may work fine for one release, but quickly break down when the GUI changes, triggering huge maintenance efforts resulting in ultimate failure. Based on the successes at CISCO, Jeff Feldstein discusses the ways they have mitigated these problems with: back-end testing without the GUI; using appropriate manual testing; simulating browsers with HTTP proxy software; and many more tricks-of-the-trade.