A Test Automation Blog

Using a selenium-grid can have many advantages, especially on bigger projects. One such advantage is that you can run many tests in parallel. Another advantage is that you only need to run your tests to one point (the selenium-grid hub). The hub will sort out if it has a connected node that is matching your request and if so, it will serve your tests to that node. Selenium grid Assumptions/preconditions You know how to download and install Java (from java.com ) You know how to download the webdrivers (also previous post) You know how to add a PATH to the PATH variable of Windows (see  Google ) Make sure Java and the webdrivers are in the PATH variable Start the hub Download the Selenium Standalone Server  and run this in the commandline: java -jar <filedir\filename>.jar -role hub Allow the firewall setting if/when this pop's up. Start the node java -jar <filedir\filename>.jar -role node This will just register the node to the hub with so...

Intro  In one of my previous blog posts, I talked about a high level view of the whole test automation setup . It happens quiet often that people that begin with test automation forget to install the webdriver or are working with an older version of the webdriver. So in this post I wanted to go over this specific part and show some examples when testing local, with selenium-grid or via appium. What are webdrivers? In short I'd say: "Webdrivers are the bridge between your test automation framework and the browser. It can mimic user behavior on the browser so that your test script perform actions like a user would do".  How does it work?  The high level view of the flow is very straight forward. Your test scripts talk to Selenium, Selenium talks to the webdriver of your needs, the specific webdriver talks to the browser. So this means you need all components. The browser, the browser specific webdriver, selenium and a program language that is supported...

In the  "installation" blogpost , I mentioned that when you install lapis_lazuli, it also installs selenium-webdriver and watir. This blogpost I want to use to explain why I use the lapis_lazuli gem as well as a small comparison between the two to show you this added value. At the moment of writing I'm using lapis_lazuli 2.0.1, watir 6.10.0 and selenium-webdriver 3.7.0 Why I use the lapis_lazuli gem? First a little background info. This gem is developed and maintained by a QA company called spriteCloud (my former employer). This is how I got introduced to this gem. The gem was first introduced on Mar 30th, 2015 . I started to use it around november 2016. And on June 29th, 2017, they posted a blog with the title "Watir, Selenium and Cucumber on steroids" . This explains lapis_lazuli in a nutshell, give it a read. Now we have a basic understanding why lapis_lazuli was created, let's have a look at some of the differences and why I like the lapis_laz...

All installations went well so by now you most likely can't wait to start with test automation. And in the next blog post we will, I promise. But I first want to teach you some handy things, give you some background knowledge to you can do it pretty much correct from the beginning. Editors It is entirely up to you which editor you use. But some have a few nifty tricks. When I started a little more over a year ago with test automation I just went with Notepad ++ . I liked the editor, I knew the editor so it was easy for me to use and to start. A friend of mine has become a fan of RubyMine   which is awesome to use since it's build for this purpose, but not free. Recently I found another editor that is free that looks promising and works very nice, Visual Studio Code . Again, I have my favorite, you might have yours, just use whatever you like most, it really does not matter. IRB If you read my previous blog post you might have noticed we already used it. But why do ...