All posts by Viktor
JUnit 5 vs Kotest. Part 2: Parameterise ‘Em All
Long time no see, ladies and gentlemen! I hope you’ve had or are still going to have good summer holidays. I’ve been quite busy lately, so this blog has got less priority than usual. But even without actual writing, many ideas of potential research and articles were still buzzing in my head. When looking into…
Documenting test architecture: Part 3 – There’s even a better way to draw your framework
Alright, ladies and gentlemen, we’ve recently discussed documenting test architecture and creating a system landscape diagram for the continuous testing process using the Structurizr tool. If you remember, we started with just 2 boring blocks on the initial chart (a QA engineer and the app under test), But in the end, it grew into a…
Documenting test architecture: Part 2 – There is a Right Way!
Alright, ladies and gentlemen! In the previous blog post, I described my recent challenge: the absence of a common approach in documenting test architecture and the potential solution to this challenge. Today, let’s take some practical steps and try to solve at least a part of the challenge using the C4 model + Structurizr bundle….
Documenting test architecture: Part 1 – Is there a right way?
Recently, I had an opportunity to visualize the continuous testing process and explain it in simple terms (possibly, without using too many words). It was challenging, first of all, because I was uncertain who would eventually see my drawing, and whether they would have enough context to comprehend it clearly. I somehow managed to accomplish…
Test Automation Days 2023: my recap of the conference
Last week, I had an opportunity to attend Test Automation Days 2023, a 2-day conference in the heart of Rotterdam about (surprise) test automation. It was quite a nice and well-organised event with interesting talks, and I had a lot of fun. Here, I’m going to write my impressions down, and, perhaps, they’re going to…
Proof of Concepts 101: how to assess your test frameworks easily
Among the various activities that test engineers perform, making proof of concepts (PoC) is essential. We create PoCs when there’s uncertainty about which process to follow, what tool or framework to use, or even when it’s an excellent time to try something new. Although it may appear spontaneous and ad hoc, creating a PoC is…
Launch of the Software Testing Today newsletter
Exciting news to be shared, ladies and gentlemen! We launched Software Testing Today together with my dear friend and colleague Ozan. It’s a weekly email newsletter about quality, testing software, industry news, and even more captivating topics to be added in future. The idea popped up in Ozan’s head first. I got really enthusiastic about…
How much time QAs should spend on staying up-to-date?
Probably, one of the biggest discrepancies I’ve seen in IT so far is a mismatch between how much companies want their engineers to know and how much time they are ready to allocate for that. The imbalance usually shifts towards the latter, meaning little to no time is officially allocated to learning new things. There…
Playwright UI mode: is it a new game-changer?
Alright, ladies and gentlemen, time for something exciting! While I’ve been trying to find some time to write a bunch of materials about the Playwright framework, its developers released a new feature: Playwright UI mode. While still being sceptical in nature, I’ve given it a try during the last couple of days and must say…
JUnit 5 vs Kotest. Part 1: Is it the new way we test?
In my previous blog post, I used Kotest framework instead of the good old JUnit and got excited about its syntax sugar and capabilities. Today, I will dive deeper into the features Kotest brings to the table and compare them with JUnit 5’s alternatives (if any). Hopefully, this article can serve as a starting point…