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

Avoiding the rabbit hole of horizontal scaling

It is important to the 80/20 rule and the rule of threes in mind. We do not want to try to support 80% of the popular browser and operating system combinations when our customers are using only 20%. It may sound pro-active to try to support Safari on Mac when our customers only use Chrome on Windows. Attempting to do a regression test in a new browser on every environment becomes logarithmically impossible. You may not have the time to execute all test cases on all browsers and all environments. We only want to test on the browsers that are used by more of our users, so that might be a maximum combination of three: one browser in two operating systems or two browsers in one operating system. In addition, time can be taken away from creating new tests if we are trying to determine the root cause of why one test runs in one browser or operating system and fails in another.