Interview with Mariusz Masewicz, the man who has seen everything [almost]

Testing code can be a bit like looking for flaws in architecture — you know it has to be done, but too often it ends with “I’m sure it should work.” Time to change that approach and stop writing ad hoc tests only to rewrite them again later.

Join us for the free webinar “utPLSQL – The Perfect Testing Tool for Lazy People”, where Sabine Heimsath will show how to put utPLSQL to work so testing becomes the most enjoyable part of software development. Instead of manually checking every “index” or “table scan,” we automate the process and sleep a lot better afterwards.

Before we meet Sabine on the webinar, we’ve got a little appetizer for you: an interview with Mariusz Masewicz.

Mariusz is a veteran who’s seen just about everything in his career — probably every possible system failure at least once. He remembers the early days of databases from real life, not from Wikipedia retrospectives. This DBA knows perfectly well that clean code is the only reliable way to avoid late-night emergency calls and nervous weekend debugging sessions.

Check out what Mariusz thinks about automation in utPLSQL and how to move from the “I test by instinct and pray it passes” approach to something solid and reliable.

Interview with Mariusz Masewicz, the man who has seen everything [almost]

How long have you been using utPLSQL for system testing? What did you use before? Do you still remember the times when testing meant running a procedure and saying: “Looks good”?

Intensively since 2017 (a project with around 6,000 tests). I remember times you don’t remember, child. :)

Do you use utPLSQL in every project? Are there situations where you skip it? Has it become like a seatbelt for you — something you simply don’t start a project without?

Did you know there’s a similar project for MSSQL Server? In both technologies, I can’t imagine life without tests — even in my day-to-day work as a DBA.

Do you write tests first (TDD), or do you add them to finished code later? In other words: classic “test-first” or “heroic coding first, panic-writing tests later”?

It depends.

In the project where you had the largest number of unit tests — roughly how many were there? And did running the full suite take seconds, minutes, or enough time for coffee and a walk?

Around 6,000 — the team expected them to finish in about the same time as a ping-pong match.

How much do you actually trust tests during refactoring? And have you ever said: “Relax, those tests have been red for ages — that’s normal”?

Tests cannot be red. And green… well, maybe they’re good, or maybe we just don’t know yet that both the test and the code contain bugs. 😊

----

Join us for our webinar!

🎙️ Speaker: Sabine Heimsath, passionate about automation and code quality.

🗓️ Data: 27.05.2026, 20:00 CEST

✅ Temat: utPLSQL – The Perfect Testing Tool for Lazy People

💰 Koszt: 0 PLN / FREE

🔗 Szczegóły: https://how2ora.pl/en/pwow

✍️ Zapisy: https://pwowwebinar3.konfeo.com/en/groups

📅 Kalendarz PWOW: https://how2ora.pl/en/pwow