Test execution automation is often seen as a technical challenge-a matter of applying the right technology, tools, and smart programming talent. However, such efforts and projects often fail to meet expectations with results that are difficult to manage and maintain-especially for large and complex systems. Hans Buwalda describes how the choices you make for designing tests can make-or break-a test automation project. Join Hans to discover why good automated tests are not the same as the automation of good manual tests and how to break down tests into modules-building blocks-in which each has a clear scope and purpose. See how to design test cases within each module to reflect that module's scope and nothing more. Hans explains how to tie modules together with a keyword-based test automation framework that separates the automation details from the test itself to enhance maintainability and improve ROI.

Cloud computing is here to stay-and it is changing the way we test software. Cloud-based testing offers flexible, scalable, and on-demand infrastructure services. And as a bonus, because the cloud offers pay-per-use purchasing options, cloud-based testing usually costs less. Tauhida Parveen describes the concept of cloud-based testing: scope, specific requirements, benefits, and drawbacks. She explains how cloud-based testing brings new capabilities and options for your testing activities-instantly creating and dismantling test environments and miming production environments in early testing. Tauhida discusses how to engineer scalable environments for load, stress, and performance testing. Then, she introduces cloud-based compatibility, cross-browser, and cross-platform testing opportunities you can exploit.

If your software product is recompiled and integrated frequently, you can improve your testing by integrating automated tests into your continuous integration process. In many organizations, unit tests are run as part of continuous integration; however, that is not enough. During the continuous integration cycle, integration of all automated tests-system, integration, unit, and regression-is vital to help find defects quickly and provide a substantial return on investment. Ayal Cohen and Roi Carmel describe the types of tests needed, the pros and cons of each type, and how to choose which tests to execute according to development code change, business criticality, and history of execution. Ayal and Roi discuss the need for service virtualization so you can run your tests in an environment that has not yet been fully developed, providing virtual substitutes for the missing services.

The role of the software tester is continuing to evolve, becoming more complex and more technical. As new methodologies, technologies, and platforms emerge, testers are bombarded with new, so-called "best practices" on how to do their jobs. The problem is that testers have heard the same songs with different lyrics for more than twenty years now. Clint Sprauve takes a contrarian’s view of testing and the quality assurance industry. He examines some of today’s typical testing "best practices"-keyword-driven testing, requirements traceability, the tester’s role in agile development, quality reporting, tool expertise, and quality certification programs-while providing alternative approaches for how to view each practice.