The framework grew – it wasn't designed.
Every change takes longer than it should, and nobody dares to touch the core structure any more.
Test platform engineering for Java and .NET teams
I modernise and build test platforms for engineering teams working on complex systems – maintainable, integrated into CI/CD and handed over so your team can run and extend them on its own.
Do any of these sound familiar? This is where I come in.
Every change takes longer than it should, and nobody dares to touch the core structure any more.
Flaky tests get ignored or re-run again and again. Trust in the pipeline erodes.
Much of the time goes into fixing existing tests instead of adding new coverage.
Results arrive too late or have to be collected by hand.
When the framework specialist is away or leaves, test automation stalls.
Teams in several locations automate in different ways. Results are hard to compare.
Three focus areas plus classic development – always aiming for your team to carry on independently.
Typical situation
An existing framework has become unstable, slow or hard to maintain.
What I do
What you get
A framework your team trusts again and can extend with reasonable effort.
Typical situation
Test automation needs to be built from scratch or set up anew.
What I do
What you get
A test platform that is developed, versioned and operated like product code.
Typical situation
Your team – or several teams in different locations – should own test automation.
What I do
What you get
Less dependency on individuals – including on me.
Typical situation
You need experienced development capacity in Java, Kotlin or .NET.
What I do
What you get
Senior support that takes product code and tests equally seriously.
Low-risk way to start: a fixed-price framework assessment – a compact review of your test automation with a prioritised roadmap. Ask for an assessment →
Selected projects, described by situation, solution and result. I'm happy to name clients in a personal conversation.
Energy technology · since 2024
Situation
An existing C#/Selenium UI test automation suite was to be replaced by a more maintainable, scalable framework generation that international teams could also work with.
Solution
Lead responsibility for designing and developing the new framework; migration to Java/Playwright; contribution to a Kotlin-based API test framework; development of a reporting and analytics platform for test results (Angular, ASP.NET Core); operation on Docker, Kubernetes and Azure.
Result
A shared basis for UI and API tests, integrated into CI/CD, with international colleagues onboarded onto it.
Railway technology · 2023–2024
Situation
An existing team needed reinforcement in test automation during a busy project phase. Tests had to run reliably across several test environments.
Solution
BDD scenarios with Cucumber and Java, glue code and test infrastructure extensions with Spring, a threading and parallelisation solution, and integration into Jenkins.
Result
Parallel execution across several test environments. According to the client's reference, a “good addition to the project” who stood out with proactive suggestions.
Enterprise client projects · 2016–2023
Situation
Reports and processes in client projects were partly produced by hand, and several systems had to work together through interfaces.
Solution
Java-based backend services, user interfaces and integrations via REST and SOAP; an automated reporting platform for manufacturer-specific cost breakdown reports; automated tests for business-critical applications.
Result
Previously manual reporting processes were automated – developed in direct collaboration with clients and business units.
“Yes, definitely. With Felix we gained a good addition to the project at a very busy time, and we would call on him again whenever needed.”
Many teams work with Selenium frameworks that have grown over years: long run times, flaky tests, high maintenance. Playwright offers auto-waiting, parallel execution, robust locators and tracing – but a migration is more than swapping tools.
I have migrated a UI test automation suite from C#/Selenium to Java/Playwright and handed the new framework over to an international team. I bring that experience to your project.
Briefly describe your situation – you'll get an honest first assessment, even if I'm not the right fit for your topic.
Felix Bliedung – Managing Director and Senior Test Automation Engineer
I have been building software for more than 15 years – first as a Java and full-stack developer on enterprise client projects, and for several years now with a focus on test automation and framework architecture.
I currently lead the next framework generation for industrial software and hardware systems in the energy sector. Before that: BDD test automation for safety-critical railway systems.
My focus is not test strategy on paper but technical delivery: I build and modernise the frameworks, platforms and integrations your test automation runs on – and hand them over to your team.
Yes. QUALENDIX is deliberately small: you work directly with me, without being handed on to other consultants.
Usually, yes. Planned on-site visits, for example for workshops or kick-offs, are possible by arrangement.
QUALENDIX DEVELOPMENT LTD is an EU company registered for VAT/VIES. Businesses in other EU countries are invoiced under the reverse-charge mechanism, as with any EU service provider.
It depends on the size and state of your existing suite. After a short framework assessment you get a reliable estimate and a step-by-step migration plan.
Yes, working through staffing partners, software houses and IT service providers is straightforward.
Tell me briefly what it's about – for example your tech stack, the size of your test suite and what slows you down most. I'll get back to you promptly with a proposed time for a free 30-minute intro call.
contact (at) qualendix.com