• Open UI Automation

    I guess all of you who have worked on UI testing know the “locator” problem. In order to find an element in the DOM you need to provide a locator and usually it’s an XPath string. Sometimes that xpath can be quite nontrivial and in one day developers change the code and your locator cannot find the required element. In order to avoid such situations as much as possible my colleagues Peter Savage, Ronny Pfannschmidt and Karel Hala have developed a specification for frontend developers Open Web UI Design Specification for Enabling Automation (OUIA). If your application complies with OUIA it will have predictable locators and the behavior. This significantly simplifies writing automated tests.

  • Making a Kodi add-on repository

    In this post I’ll explain how to create your own Kodi add-on repository, deploy it on Netlify and automate that workflow.

  • Evolution of UI testing

    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.

  • Pipelines speedup

    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.

  • Gitlab CI shared pipelines

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