Book Image

Enhanced Test Automation with WebdriverIO

By : Paul M. Grossman, Larry C. Goddard
Book Image

Enhanced Test Automation with WebdriverIO

By: Paul M. Grossman, Larry C. Goddard

Overview of this book

This book helps you embark on a comprehensive journey to master the art of WebdriverIO automation, from installation through to advanced framework development. You’ll start by following step-by-step instructions on installing WebdriverIO, configuring Node packages, and creating a simple test. Here you’ll gain an understanding of the mechanics while also learning to add reporting and screen captures to your test results to enhance your test case documentation. In the next set of chapters, you’ll delve into the intricacies of configuring and developing robust method wrappers, a crucial skill for supporting multiple test suites. The book goes beyond the basics, exploring testing techniques tailored for Jenkins as well as LambdaTest cloud environments. As you progress, you’ll gain a deep understanding of both TypeScript and JavaScript languages and acquire versatile coding skills. By the end of this book, you’ll have developed the expertise to construct a sophisticated test automation framework capable of executing an entire suite of tests using WebdriverIO in either TypeScript or JavaScript, as well as excel in your test automation endeavors and deliver reliable, efficient testing solutions.
Table of Contents (20 chapters)
16
Epilogue
Appendix: The Ultimate Guide to TypeScript Error Messages, Causes, and Solutions

The multiverse – one test, two environments

The advantage is that these IfExist() methods will not stop the test if the object doesn’t exist. Our tests can now be executed in a test environment where new functionality exists, as well as a production environment where the functionality is yet to be pushed. For example, a page may ask for a month to be selected from a list on a long survey navigation path. In the staging environment, this requires the Next button to be explicitly clicked to move to the page. However, in QA, the Next button is removed and the page implicitly moves on once the user selects an item from the list:

Helpers.clickIfExists(await this.btnNext);

There are two approaches to this implementation. First, we could enhance the clickadv() method with an optional property:

export async function clickAdv(element: WebdriverIO.Element, ifExists: boolean = false) {
// isExist code branch here ...
}

However, this leads to code that is less clear about...