Book Image

Testing Practitioner Handbook

By : Renu Rajani
Book Image

Testing Practitioner Handbook

By: Renu Rajani

Overview of this book

The book is based on the author`s experience in leading and transforming large test engagements and architecting solutions for customer testing requirements/bids/problem areas. It targets the testing practitioner population and provides them with a single go-to place to find perspectives, practices, trends, tools, and solutions to test applications as they face the evolving digital world. This book is divided into five parts where each part explores different aspects of testing in the real world. The first module explains the various testing engagement models. You will then learn how to efficiently test code in different life cycles. The book discusses the different aspects of Quality Analysis consideration while testing social media, mobile, analytics, and the Cloud. In the last module, you will learn about futuristic technologies to test software. By the end of the book, you will understand the latest business and IT trends in digital transformation and learn the best practices to adopt for business assurance.
Table of Contents (56 chapters)
Testing Practitioner Handbook
Credits
About the Author
Acknowledgement
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Index

Chapter 7. Testing in Agile Development and the State of Agile Adoption

Agile development has accelerated in the last decade due to increased digital adoption creating a need for more continuous integration. In this chapter, we will discuss Drivers for the use of Agile:

  • The promise of agile as compared to waterfall

  • Various flavors of agile—for example, Kanban, Scrum

  • Testing in agile sprints

  • Agile in distributed environments

  • State of agile adoption

  • Approaches to testing in agile development

  • Skills needed by QA professionals in Agile engagements

A thought must be striking to you readers that why use Agile development?

Organizations are increasingly struggling to reach the right level of quality versus speed. Some key issues with traditional development and testing include the following:

  • Excessively long time to market for products and applications

  • Inadequate customer orientation and regular interaction

  • Over-engineered products--most of the features on a product or application may not be used

  • High project...