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 WebdriverIO project with Jenkins

From the main dashboard view, click the + New Item button. Jenkins provides us with several project options and organizational tools. Freestyle project is a streamlined approach to building a job, while Pipeline allows more granular customization with the Groovy programming language:

Figure 15.11 – Creating a Freestyle project

Figure 15.11 – Creating a Freestyle project

For our purposes, Freestyle project will suffice. Several options will be displayed. We will only need a few to get our first test from Chapter 2 to be checked out of our GitHub source control manager (SCM) and run:

Figure 15.12 – Adding build steps

Figure 15.12 – Adding build steps

Under the Build Steps section, select Add a Build step to execute terminal commands. For Mac, select Execute shell and for Windows, choose the Execute Windows batch command option. Using the command prompt, we will navigate to the workspace path.

Next, add a run a npm command build step. This is...