Recently, I have had thoughts about how we approach testing, especially testing from a user’s side. “Selenium will save us”, they said, and yes, Selenium helps a lot. But when the initial dust settled, we found that there was no Holy Graal. What is bad about Selenium? There are many problems, but all of them are just consequences of the one main problem. For Selenium the application under test is a black box and this is the main problem. It’s the reason for all of the pain people go through when applying web application testing using Selenium. ...

Recently, I helped our network team with load testing for our balancers for static content. My default choice for a long time was Gatling. It’s a great tool for the job, it’s easier to start with than JMeter, for example. You are capable to easily create scenarios and put logic into them, thanks to Scala. But recent events made me think that where is far more tools for different tasks. The problem with Gatling that I encountered was this: See those declines on the picture? It seems to be a garbage collection. For most tasks that I performed this wasn’t a problem, but for balancers it was required to create a stabile load. Because of this, I started looking for other tools. ...

Hi, this is a first post on my blog.