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

Disadvantages


While weekend testing is an interesting and evolving phenomenon, there are concerns, including the following:

  • Inadequate security: Weekend testing does not undertake adequate measures to secure customer IPs, secure an ODC, sign NDAs, and so on, which is generally practiced by customers dealing with offshore service providers. Testing is usually done in an informal and relaxed environment; this could make clients feel skeptical about sharing their IP.

  • Inadequate alignment with business: Weekend tester forums may not be able to swiftly respond to changes in strategy taken by customers during the project. Lack of a proper governance model and transition methodology hinders weekend testing projects from responding to changing customer needs. It may therefore pose a risk to project delivery, particularly to brand new implementations.

  • Inability to adopt DevOps: Weekend testing relies more on open source tools and manual testing and therefore does not align well with DevOps delivery...