Automated GUI tests often fail to find important bugs because testers do not understand or model intricate user behaviors. Real users are not just monkeys banging on keyboards. As they use a system, they may make dozens of instantaneous decisions, all of which result in complex paths through the software code. To create successful automated test cases, testers must learn how to model users' real behaviors. This means test cases cannot be simple, recorded, one-size-fits-all scripts. Jamie Mitchell describes several user behavior patterns that can be adopted to create robust and successful automated tests. One pattern is the 4-step dance, which describes every user GUI interaction: (1) ensure you're at the right place in the screen hierarchy; (2) provide data to the application; (3) trigger the system; and (4) wait for the system to complete its actions.

Test managers constantly lament that few outside their group understand or care much about the value they provide and consistently deliver. Unfortunately, they are often correct. The lack of visibility and understanding of the test team's contribution can lead to restricted budgets,
fewer resources, tighter timelines, and ultimately, lower group productivity. Join Theresa Lanowitz as she highlights ways to move from simply being a tester of software to an advocate for your organization's customers. Learn how to effectively and concisely communicate with key
stakeholders in your organization to ensure that they understand the value and role of the testing group. With effective and concise communication, the testing group will be perceived as more strategically important and integral to the success of every project.

• Strategies for communicating complex data

These days outsourcing is a pretty familiar concept in this industry. Has globalization hit your company yet? Naomi Mitsumori has been involved in sending testing work offshore, and she has six suggestions that can help you successfully manage the transition.

Afraid of what you're missing by testing only 7 percent of your code? Forget your formal code inspections; Jason Cohen enlightens us on the merits of bringing lightweight code inspection to your organization.