Web UI testing is a tricky thing in many aspects. They requires many dependencies, they are slow and they are often flaky. In this post I would like to share my web UI testing experience on an example of one python library.

Often when you want to run some tests you need to install required dependencies such as python packages, ruby gems, npm packages and so on. Nowadays tests are executed automatically for pull (merge) requests in various CI systems. Dependency pulling is repeated again and again for every test run and it takes time. We cannot do much about it in cloud based CI systems such as Travis, Circle CI or Github Actions but there is some space for improvement for self-hosted Gitlab CI, Jenkins and others.

Imagine you have a group of repositories in Gitlab and you would like to have the same pipelines for whole group.

When you test your web application with Selenium there is a one fundamental problem. Due to dynamic nature of modern web pages you cannot interact with elements on the web page immediately after loading. What can we do with that?

I guess everybody knows Jenkins. It's one of the oldest and well-known automation system. It was developed in the times when there was no Docker, Kubernetes, cloud native and other buzzwords. I familiarized with it when I started to work at Red Hat. After a couple years of using I have some concerns I want to share.

Debugging is an essential part of programming. I guess you can agree with me that it takes significant amount of time. Using an appropriate tool can save your time and efforts.

I've been using Linux for 11 years already. I've tried several Linux distribution in both desktop and server use cases. I wouldn't call myself a distrohopper but I've collected some observations about some popular Linux distributions.

In programming it's quite often you need to wait for an action to complete or some service availability. There are many ways and tools which able to do that. I would like to tell about two python libraries I've worked with.

I'm pretty sure most of you familiar with Gitlab. It has a lot of features and nowadays it looks a bit bloated but one thing I really love in this tool. It's Gitlab CI. One of the coolest thing there is it can run jobs on many platforms including virtual machines, Docker containers and Kubernetes.

As a quality engineer I responsible for testing various parts of a product. One of such part can be the web UI. But before your first UI test will be executed you will need to configure a lot of things. It might be a non-trivial task. Kubernetes can be quite helpful here and be actual "one ring to rule them all".