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

Creating a freestyle project and job

From the Jenkins dashboard, click + New Item. This provides us with several options, including Freestyle project and Pipeline. The Freestyle project option is for beginners, while the Pipeline option is for advanced users who wish to create a custom pipeline script in Groovy. Let’s begin by entering Enhanced Test Automation with WebdriverIO as the name and selecting Freestyle project.

This will display several tabs, including General, Source Code Management, Build Triggers, Build Environment, Build, and Post-build Actions. We will choose to run using code from our local machine. Advanced users can use a cloud-based corporate Jenkins to check out code from a private repository:

Figure 15.15 – Setting up custom state-based test runs for manual testers

Figure 15.15 – Setting up custom state-based test runs for manual testers

To run the build, we need the name of the test and the path to the project directory.

Parameterizing

In the job configuration, we will add a parameter...