TL;DR

Browser test automation made a long path from the initial selenium project commit. Since then, the selenium project is supported in various programming languages. As we do not think that you should lock your Browser automation project with the programming language of the leading project, we decided to write a series of blog posts about Browser automation using Ruby and appropriate Ruby Gems. If you find this project useful, please star it on Github.

Chapter 01

In chapter one, we will install tools and prepare a basic project structure. Head to the install section and run those commands. This will install ruby 2.6.5 using Ruby Version Manager. Gem libraries are:

• cucumber – Gerkin feature files test runner.
• RSpec – Ruby de facto standard testing framework. We will use its reach expectation library
• page-object – implementation of page objects. Depends on the awesome Watir project.
• Watir – resolves all important problems with webdiver lower-level API
• webdrivers – it keeps your webdrivers up to date.
• Faker – helps you to create realistic test data sets.
• rest-client – send rest API calls.

Now its time to set up a cucumber basic project structure. Run:

cucumber --init

In this commit, you can see all the relevant files.

We are ready for chapter 02!