Saturday, January 12, 2019

Adding console error log verification to Selenium tests using Chrome



Contents:

1) Introduction
2) Preparation
3) Demo

1. Introduction

Selenium is an amazing test tool that is used pretty much everywhere these days. People are usually so spoiled by the number of functionalities it provides that they can't hide being surprised when they notice two missing functionalities:
  • ability to assert HTTP requests/responses (like status codes)
  • ability to capture browser console logs
Today I'd like to focus on the second topic - browser console. 

To put it in simple words. Currently, you can easily capture browser logs only in Chrome. Of course, you can always build your own solution for other browsers but you have no guarantee that it would work after next browser update. There is a W3C Webdriver attempt to standardize browser logging interface however the progress seems to be slow.

Thankfully, in Chrome errors can be captured and I encourage you to do it in your scripts.

2. Preparation

To show this feature in action we need to prepare tests. I'm going to use my own blog as an example of a site not reporting any console errors. In order to make failing example deterministic I created a custom broken site.

As usual, tests are written using FluentLenium.


3. Demo

Capturing console log errors is pretty easy. You only need one method


And as you can see on the image below error was reported.


Every line of code needed to write this blog post was added to my GitHub project.

Happy new year everyone :)

No comments:

Post a Comment