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

Background – Behavior-Driven Development (BDD)


In the Agile/DevOps environment, the features of the product/application being developed are co-engineered by business analysts, vendors, development, and the testing team. Given the engagement structure where various technical and non-technical members work together, a plain English construct for scripts comes in handy. Such constructs have little structure, and are very easy to learn even by non-programmers, yet structured enough to allow precise description of test examples to show business flows.

One such language using plain English construct is Gherkin. One can develop the tests using Gherkin languages and create a .feature file containing the executable specifications for the behaviors expected. Then a tool like Cucumber can be used to execute/test the features.

In this section, we will touch upon a plain English-like construct of the Gherkin language for BDD in the Agile/DevOps environment and discuss various activities and roles involved...