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

Increased Flexibility – Writing Robust Selectors and Reducing Maintenance

Maintenance is the ever-growing villain of a test automation project. Each release has more tests and more elements that can go stale, causing a test to fail. If you are new to the test automation field, you may not realize just how much maintenance will increasingly impact your project release after release. I (Paul) would like to share with you this story that inspired several unique solutions.

Several years ago, my client’s development team decided to change the entire underlying architecture supporting the application under test. My automation team only became aware of this change when we found nearly all 100 of our test cases suite failed to reach a passing state. In fact, the only test case that passed was the LogIn test we wrote on the first day of the project. We realized that hundreds of element objects had changed their tag name to different types and used different properties. We were...