Getting started with test automation?
A good foundation prevents many problems later on.
Test automation that actually works. Quality built for your needs.
Many teams get stuck on the same three problems
100
100
100
Why are CI/CD pipelines often slow?
Pipelines are often slow because not everything runs in parallel. Everything is rebuilt, and with every change, all tests run. This often results in late feedback.
Tests can become flaky in CI/CD for a variety of reasons. Here are some common ones: * **Race Conditions:** These occur when multiple parts of your code, or even external services, try to access and manipulate the same resource simultaneously. The outcome depends on the precise timing of these operations, making the test results unpredictable and therefore "flaky." This is especially common in concurrent or asynchronous testing. * **Dependencies on External Services:** If your tests rely on external APIs, databases, or other services, and these services are unavailable, slow, or return unexpected results, your tests can fail intermittently. Issues with network connectivity or the stability of these services themselves can cause flakiness. * **Inconsistent Test Environments:** CI/CD environments can sometimes differ slightly from development environments or even between different CI/CD runs. Differences in operating system versions, library versions, system configurations, or available resources (like memory or disk space) can lead to tests behaving differently and failing unpredictably. * **Test Data Management:** If tests create or modify data, but don't properly clean it up afterwards, subsequent test runs might be affected by the leftover data. This can lead to tests failing because they are operating on data in an unexpected state. Alternatively, if test data generation is not deterministic, you might get different data each time, leading to different test outcomes. * **Unreliable Test Setup/Teardown:** If the setup phase of a test doesn't complete successfully or the teardown phase doesn't clean up resources properly, it can leave the system in a state that causes subsequent tests to fail. * **Timeouts:** Tests that rely on operations completing within a certain timeframe can become flaky if those operations are occasionally slow due to network latency, slow external services, or underperforming test infrastructure. If an operation takes just a little too long, the test will time out and fail, even if it would have passed under normal circumstances. * **Non-Deterministic Code:** Code that uses random numbers without controlling the seed, or relies on system clocks in tests, can produce different results each time it's run, leading to flakiness. * **Asynchronous Operations:** Testing asynchronous code without proper synchronization mechanisms (like waiting for specific events or states) can lead to tests asserting conditions before the asynchronous operation has actually completed. * **UI/Web Automation Specifics:** * **Page Load Times:** Tests interacting with web interfaces can be sensitive to how quickly pages and elements load. If a page loads slower than expected, the test might try to interact with an element that isn't ready yet, causing a failure. * **Element Locators:** If element locators (like CSS selectors or XPath) are brittle and change without corresponding test updates, tests can break. Dynamic IDs or classes can also contribute to this. * **Browser/Driver Differences:** Minor variations in how different browsers or browser driver versions render or behave can cause tests to fail intermittently. * **Resource Contention:** In a CI/CD environment, multiple builds and tests might be running concurrently. If your tests consume significant resources (CPU, memory, disk I/O), they might compete with other processes, leading to slower execution and potential timeouts or unexpected behaviour. * **Lack of Proper Isolation:** If tests are not properly isolated from each other, one test might affect the state of the system in a way that causes subsequent tests to fail. Addressing flaky tests requires careful investigation to pinpoint the root cause. Strategies often involve implementing better synchronization, ensuring deterministic test data and environments, improving test isolation, and making tests more resilient to minor fluctuations.
Tests are flaky because they rely on things that aren't always the same. Each run is different. As a result, they sometimes fail and sometimes pass, for no clear reason.
Why test automation is often not maintained
Test automation is often not maintained. It becomes too complex, only QA still understands it and teams use it less and less. As a result, it loses its value.
Recognisable?
These are precisely the problems that cause teams to lose faith in their test results.
How I solve this
Build a test automation framework
I build test automation frameworks that remain maintainable. So that teams can use and extend them themselves.
Integration into your CI/CD pipeline
I configure pipelines so that feedback is quick. So that only what is needed runs and results are clear immediately.
Make your team stronger with qa workshops
I train teams in test automation and best practices. So that they can set up and maintain tests themselves.
From test framework to complete QA infrastructure
Most teams already have tests. But they run at the wrong times, fail for no reason, and no one reads the results. I fix that, not with more tests, but with the system around them.
Automated test environments
Test environments spin up automatically before each run, and are torn down straight afterwards. No manual work, no unnecessary costs.
Smart CI/CD pipelines
The pipeline builds the environment, runs the tests, and cleans everything up again. Automatically, with every code change.
AI-driven insights
After each run, AI analyses the results and sends an understandable message to Slack. For developers and management.
Automated reports
Each report is automatically saved with a version number. Always findable, nothing disappears.
Want to get better at test automation?
In my workshops, you will learn how to set up an automation framework, write tests and integrate them into CI/CD pipelines - at your level, whether you are junior, medior or senior.
What customers say:

Super collaboration!
We have worked together before, and this time did not disappoint either. Clear communication, sharp solutions and a solid test framework in no time. Just well organised, as we are used to.

Everyone happy - from dev to stakeholder!
Our CI/CD pipeline is running like clockwork. The tests created with UiAutomator2 are running every day. The integration was very smooth that even the stakeholders immediately realised how much time and frustration we now save.

Clear, practical training that really sticks
The workshops were spot-on - hands-on sessions in Playwright, Cypress, and GitLab that gave our team exactly what we needed to get confident and independent. Rody is a great teacher and takes the time with his students.
Super useful from day one!
Customised test automation framework - for UI and API testing
I develop test automation solutions that provide faster feedback, fewer bugs and give you more grip on quality. Whether it's Cypress automated testing, Playwright automation or REST API validation - I help teams set up and extend their test automation in smart way. I also integrate performance testing seamlessly into your CI/CD pipeline.
As a freelance software test automation engineer, I build test automation frameworks that are scalable, stable and future-ready - from automated software testing and regression suites to deploying modern test automation tools and frameworks.
I build test automation frameworks that fit your team and your way of working.
14+ years of experience in test automation customisation
With 14 years of experience in test automation, I know what works - and what doesn't. Every project requires a different approach. As freelance test automation engineer I work with tools such as Cypress, Playwright, Rest Assured and K6. From building a solid test automation framework to training your team: I make sure your testing process becomes scalable, maintainable and future-proof.
Thanks to CI/CD integrations and clear reporting, stakeholders remain continuously informed. So you not only get a grip on quality, but also quick feedback during every step of your release process - whether it involves automated software testing, API automation, load testing or regression suites.
No standard solutions, but bespoke ones. So that you can build with confidence and test without worries
Ready to take your test automation to the next level? Feel free to send me a message!
14 years of test automation experience
Senior software test automation engineer with in-depth experience in setting up CI/CD pipelines, creating/maintaining test automation frameworks and training QA automation teams.
K6 performance mastery
K6 load testing expert - I help you discover bottlenecks before going live, with performance tests on your APIs, running in your CI/CD process!
CI/CD specialist
Expertise in setting up CI/CD pipelines with tools such as Jenkins, GitLab, Azure DevOps and GitHub Actions. Full automation of regression suites within your release process.
QA Automation Training
Hands-on training for QA automation testers. Learn to automate testing yourself with Cypress, Playwright and API testing frameworks. Perfect for teams as well as individuals.
My work process
01
1. Discuss the challenge
Understanding your problem. Together, we look at what automated testing solutions fit your team and technique.
02
2. Planning & Design
We tailor an approach, including a timeline and the right test automation tools and frameworks for your project.
03
3. Development & Implementation
Develop and implement the test automation framework, aligned with your CI/CD, APIs and UIs.
Â
04
4. Testing & teaching
We test the framework with real use cases (UI & API automation testing) and train your team in its use.
05
5. Launch
The automation framework will be integrated into your daily processes, with support for a smooth start.
06
6. Maintenance
I provide updates and maintenance so that you automated tests keep running reliably - release after release.
Companies I have helped
Featured
My blogs have appeared on the K6 website, including the article "Turning data into understandable insights".
I also gave a seminar for Xray and was highlighted on Techworld's blog with Nana.
Testing without stress?
Yes please.
Ready to take your test automation to the next level?Â