Skip to main content

Automated browser testing in 2018

Every now and then I do some research on browser testing. More specifically I try to find and evaluate what kind of ready to use solutions or libraries have emerged since my previous research or if some of the previously tested solutions has come up with something new.

Back in September 2017 I had some extra time on my hands and I used a couple of days to see what are the new and interesting solutions at that time. I came across some tools that I have used in the past and found two new interesting options in which one stood out.

Say hello to TestCafe


The most interesting solution that I found was called TestCafe. It's a open source Node.js library from a company called Developer Express Inc. They also have a commercial product called TestCafe (confusing) which I haven't tried as the open source library provided everything I was interested in and it seemed to be under active development.

The thing that caught my interest at first was that this library doesn't depend on WebDriver i.e. the API used by Selenium. All the browser testing tools that use real browsers and I have tried before have been dependent on WebDriver API meaning that even if the tool itself is e.g. a Node.js library it still needed to run the WebDriver Java API in the background.

Another thing where TestCafe excels compared to it's rivals is it's browser support. Basically all major browsers and operating systems are supported.

Writing tests with TestCafe


As TestCafe is a Node.js library the tests can be written in JavaScript and the library also provides TypeScript support. I've written a example with three test cases that can be found from my github repository, the last one fails on purpose to demonstrate failure reporting.

TestCafe uses a concept called Selectors for selecting DOM elements to test or to execute a action on. In addition it provides a concept of client functions that adds the ability to read data from client side e.g. the current URL of the browser window.

Running tests


Given that TestCafe is a Node.js library the tests can be executed with node as simply as running command npm test. Another option is to execute the tests in a docker container which is a great option for CI servers. I have created examples and instructions of both in my github repository.

Real life experiences


I have been using TestCafe in a work project since November 2017 to run browser tests locally with Node.js and in CI within docker. So far I have been very impressed on how good the performance and stability have been compared to previously used solutions. I'm still going to keep my eyes open for old and new rivals but for now I consider TestCafe to be the solution that I'll be using and comparing others to.

Other solutions to consider


Commercial tool from the same company Developer Express Inc. also called TestCafe. I haven't tried this one so I can't really say anything about it.

Cypress.io is another new tool that runs without WebDriver. This one supports only Chromium based browsers and I couldn't get anything but their own examples to run so my experience with this one wasn't so great.

Comments

  1. Thanks for the review! Here is an explanation of TestCafe version history:

    https://testcafe-discuss.devexpress.com/t/what-is-the-difference-between-the-open-source-version-and-the-paid-version-of-the-testcafe/253/2

    ReplyDelete
  2. Anonymous25/9/18 13:35

    I liked your article and its very interesting and thought that you might be interested in LambdaTest. LambdaTest is a newly launched cross-browser testing tool gaining popularity among testers community.

    Since you've already written a post on it, so I thought to introduce you to it. You can give it a look here: www.lambdatest.com. Please include this in your post if you think it deserves to be here.

    ReplyDelete

Post a Comment

Popular posts from this blog

Simple code: Contracts

Code works around contracts and contracts should be carefully thought and crafted. What are contracts A High abstraction level of contracts for code are API's. They define a interface that is basically a contract that the producer and consumer of the API agree to use to communicate with each other. Two common forms of API's are libraries that are used in code and external API's  that are used via HTTP, RPC etc. When thinking in a bit deeper contracts consist firstly of functions, methods or external endpoints and secondly of data, more precisely on data models and data types within the models.   Defining contracts Contracts should always be defined with careful thought. I've come accross few times to someone saying that "this is for intenal use only so it doesn't need to defined and/or documented as thoughtfully as a public API would be" but I disagree with that. The same care should be be given to internal and external contracts because the contracts are

Simple code: Functions and methods

What makes a good function or method? I don't think it's a single thing but a combination of things where each is significant. If one the things is flawed it affects to all others and the whole function is flawed. So what are those "things"? Have a meaningful name Function should have a name that describes it's purpose or functionality. When a function has a meaningful name it's easy to read and understand what's it's purpose. Let's take a example. If function's purpose is to find a customer by it's id a good name could be findCustomerById(id: String) or it could just as well be just  findCustomer(id: String) because the function signature implies that the customer is found by it's id the word find also implies that the customer might be found or it might not be found. If the function's name would be changed to getCustomer(id: String) it's meaning changes because now it implies that there's no fallback, the customer is e

DIY home automation, new generation

I've had my DIY home automation system for controlling outlets and reading sensor data running for about two years now. The system has been working fine and I haven't had any need to touch the code since I added the sensor reading to it, until a few months back. Need for new functionality Few months ago I got a new IoT toy for a lend from a friend until I'd get my own toys, a ruuvitag sensor beacon. Ever since I found the ruuvitag for the first time from kickstarter I had the idea of getting a bunch of ruuvitags and adding their weather station sensor readings as part of my home automation system. The original home automation backend included only tellstick compatible devices and was written in Python, and in my mind it was kind of a hack. The ruuvitag beacons communicate via BLE i.e. Bluetooth Low Energy and that meant that I needed to add functionality to read the beacon data via bluetooth. I found a ruuvitag Python library and initially thought that I'd just