Automation Testing : Anti-pattern with Cross browser checking

Par Marie Krust

19 Apr 2017

Written by: Mark Winteringham 
Recommended reading by Stefan Papusoi, Test Specialist at q-leap

“Using the same automated check for all browsers means you are probably going to miss some browser specific aspects. So why not take that into account and look for the correct information. Avoid the anti-pattern”, Stefan Papusoi Test Specialist at q-leap pointed out.

Recently I was reading a discussion on the Testing community’s automation slack channel in which one of the members was asking others about options around extending their smoke checks to run against multiple browsers. The others gave great advice around using tools such as Sauce labs or Virtual machines which are perfectly valid, but unknowingly they fell into a trap. They were demonstrating what I believe is an important anti-pattern when it comes to checking which I want to discuss today.

What is this anti-pattern why is it an anti-pattern?

Consider we write a check that does the following using WebDriver that we want to run across different browser:

  1. Complete and submit a plain HTML form
  2. Assert that the backend redirects us to a new page

Running this check across multiple browsers is the anti-pattern. Why? Well it boils down to what it is we think we are checking, so let’s take a look at some different assumptions we could make about what we are checking:

  • Checking that each browser renders the form correctly so it can be filled in by a human […]
  • Checking that each browser takes us to the same page after submission […]
  • Checking that each browser is using JavaScript correctly to create the form […]

Read the full article here.

About our q-leap’s expert recommending this Article

Stefan Papusoi is a Test Specialist at q-leap. As a Context Driven and Exploratory Tester, he is constantly increasing his experience in testing, automating scripts, and managing and improving the testing processes.


Leave a Reply