For a few years, when it got here to automating net UI testing, Selenium was the king. And it’s protected to say it nonetheless is! As a extensively identified and confirmed automation testing instrument, it’s typically a default selection for a lot of software program tasks. However does it imply one shouldn’t discover different applied sciences and frameworks? After all not! On this article, I’ll talk about the details behind using Protractor and clarify set it up for seamless use with Cucumber and Web page Object Mannequin.
To start organising the venture, first, you’ll want to put in node.js. After putting in it in your machine, you possibly can confirm that the set up was profitable by typing in ‘node -v’ within the terminal. Whilst you’re at it, in the identical place it’s also possible to confirm the Node Packages Supervisor, typing in ‘npm – v’. Then, sort in ‘npm set up -g protractor’ and confirm its profitable set up with ‘protractor –model’. Simply in case, you possibly can replace the driving force every now and then by utilizing the “net driver-manager replace” command.
Our subsequent step will probably be organising the IDE for snug work. First, in Visible Studio Code set up the “Cucumber (Gherkin) full help” extension. As soon as that’s performed, now we have to handle our dependencies. In our venture’s bundle.json file we’ll want to incorporate chai and chai-as-promised for assertions, cucumber, and protractor – all within the dependencies part. In devDependencies, we’ll want protractor-cucumber-framework to realize the aim we’re striving for.
To have consolation and readability throughout the growth course of, one of many options that present it’s the capability to rapidly search for what code is executed behind every gherkin step. To realize that in a Protractor venture, we’ll have to specify Cucumber choices within the conf.js file. What is critical is the trail to the steps folder.
Then, within the settings.json file, we’ll have to specify the paths to folders containing step definitions and strategies which can be executed behind them. We will do that within the following method:
After we do that, we will simply navigate via the venture by clicking the step/definition/technique/aspect specified within the code with a CTRL or CMD button pressed. It’s a easy factor, however it could possibly dramatically increase productiveness and reduce the time spent on growing or debugging assessments!
Our subsequent premise that we have to sort out is operating the assessments by tags. Whereas including a tag to a characteristic file is fairly simple, the half the place these are run requires offering a path to Cucumber Function information within the conf.js file.
As you possibly can observe within the above piece of code, the cucumberOpts part within the conf.js file requires a variable named ‘tags’ as an empty checklist.
Whereas we’re at it, it is very important level out that the conf.js file must have a bit the place we specify the Cucumber as our testing framework:
The general construction of the automated testing venture created in Web page Object Mannequin is analogous throughout applied sciences. An outline for Protractor will be noticed under:
When you create all the mandatory information and end the configuration, it’s time to write the assessments themselves.
Since we’re working in BDD framework, let’s begin with a easy Function File with a easy state of affairs specializing in verifying a Registration kind (with a tag for operating it later)
As soon as that’s performed, we will specify what occurs in every step in /steps/registration.js:
In that file, we first specify the trail to the file containing strategies which can be going to be known as in every of the step definitions. Then we’re calling assertion libraries and organising timeouts.
Step definition implementation is fairly simple; the Cucumber key phrase precedes a regex and a parameter; the physique of a step calls a technique from /pages/registration.js file. Often, one step calls for only one technique however take a look at steps may very well be extra intricate if want be. Discover that if a technique returns a Boolean worth, we’re invoking assertion on the degree of a step definition (line 23).
Within the/pages/registration.js file, we have to specify a locator dictionary for parts that we’re going to work together with. You are able to do this within the following method:
Please observe the selectors used for finding the weather; you should use varied out-of-the-box strategies for finding parts in Protractor, which have been extensively described within the official Protractor Information (link)
The identical goes for strategies used to work together with parts:
(PS. Don’t retailer your login credentials within the take a look at automation code… The above is only for demonstration functions)
What occurs above is that we’re implementing strategies that we’ve known as in /steps/registration.js file, utilizing the weather we’ve put within the locator dictionary (highlighted in mild blue) and interacting with them utilizing Protractor strategies (highlighted in purple).
Then it’s time to run the assessments. In VS Code, open a brand new terminal window and hit the “net driver-manager begin” command. Webdriver ought to be up and operating now.
To run the take a look at you’ve written and tagged accordingly, all it’s worthwhile to do now’s you must open one other new terminal window in VS Code and enter the command:
protractor protractor.conf.js –cucumberOpts.tags=’@smoke1′ – tagging the specified characteristic accordingly.
And there you’ve got it! Now you’ve got a prepared, arrange Protractor testing framework built-in with Cucumber, Web page Object Mannequin which you’ll be able to run with the assistance of tags. If you wish to discover out extra about Protractor, I encourage you to go to the Protractor web site, which accommodates complete documentation with code examples here.