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 25. How Should a Tester Adapt to Cloud – Call for Change of Mindset among Testers

The dawn of the digital era brings a new set of challenges for companies today. With cloud, mobile, analytics, and social media forming the cornerstones of digital transformation initiatives, unanticipated obstacles often appear along the road to digitization. These digital roadblocks may stall the overall digital evolution, sending developers back to the drawing board to draft alternate routes around the problem. Finally, these obstacles may actually be the product of individuals seeking to bring such digital initiatives to life.

In the past, testers have relied on well-maintained applications and a scope of testing limited to both functionality and the ability to scale. The traditional way of testing was to work on requirements, create a test strategy, design test cases, and then execute them in a closed environment. This testing almost always lacked certain infrastructural components; such elements...