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

Self-healing elements

With custom method wrappers, we can now start to work to reduce the required maintenance in our framework with self-healing elements. These are elements in a user interface that automatically recover from issues without the need for updating the page object model. This can include link elements that have become invalid because the class has changed since the last release. Self-healing elements are designed to improve the testing experience by reducing the need for manual input and allowing the test a better chance to run to completion.

For example, let’s say the Login button in the last release was a link:

  public get lnkSubmit() {
    return $('//a[text()="submit"]');
  }

After this, we call the button that is no longer valid:

    // Class switching
    await helpers.clickAdv(this.lnkSubmit);

Normally, if this element were clicked, it would...