Test automation teams are typically created with the expectation of facilitating faster testing and higher product quality. To achieve these goals, the test
automation team must overcome many challenges--stale test data, burdensome test script maintenance, too-frequent product upgrades, insufficient resources, and unfamiliarity with the systems under test. Satya Mantena describes a creative approach to test automation that overcomes
these challenges. The first step is implementing keyword-driven testing. Satya demonstrates how the keyword testing approach is implemented proving this approach is not just theory but has been "proven in action." Satya concludes
by showing how positioning the test automation team as a "product" rather than as a central service, or embedded within each testing team, results in better testing.

• Examine the difference between a service and a product

People forget things. Simple things like keys, passwords, and the names of friends long ago. People forget more important things like passports, anniversaries, and backing up data. But Lee Copeland is concerned with things
that the testing community is forgetting--forgetting our beginnings. We forget the grandfathers of formal testing and the contributions they made. We forget organizational context, the reason we exist and where we fit in our company. We forget to grow, to learn, and to practice the latest testing techniques. And we forget process context, the reason that a process was first created but which
may no longer exist. Join Lee for an explanation of these nine "forgettings", the negative effects of each, and how we can use them to improve our testing, our organization, and ourselves.

• Learn how we must constantly rediscover

A look back at the life of Bill Elmendorf.

A tester can use a Web browser all day to conduct functional testing, but a browser won’t provide much detail or insight on its own. Learn how to improve your functional Web-testing capabilities on a budget with thes $60 Web-Testing Toolbox.