Oh, Marionette, My Dear

When I was running a UI test locally I encountered this in the log file:

[exec] INFO: Retrying request to {}->http://localhost:14804
[exec] Jul 30, 2018 10:17:34 AM org.apache.http.impl.execchain.RetryExec execute
[exec] INFO: I/O exception (java.net.BindException) caught when processing request to {}->http://localhost:14804: Address already in use: connect

Sometimes even the was hung and the browser was closed after a while. So basically I couldn’t execute a single UI test locally that frustrated me.

I will say a few words about the environment I work with. “There is no use saving it until later.” (To use the words of  Richard Brautigan’s words, which is a favorite sentence of mine from ‘In Watermelon Sugar’.)

The test framework I work with is based on top of Selenium Webdriver, it is an extra layer – please don’t ask why. The implementation of this framework is done by another team. Details are overspread, so a lot of digging required if I want something to know.

Spoiler alert!
This framework is launching Firefox 52 by default.

Continue reading Oh, Marionette, My Dear


Quarantining failing tests is similar to death sentence

There may be times when you want to prevent a failing test from causing the whole build to fail so you put failing tests into quarantine.
You have the assumption that when you have time, you’ll fix up those failing tests. Or someone else will do it.

The reality shows a different picture.

Why are tests quarantined?
Tests can end up in quarantine when it is thought to be flaky for example, or a part of the component is being rewritten which is still in progress so that tests would fail, yet the code has to be merged in, etc.

Continue reading Quarantining failing tests is similar to death sentence