Test platform engineering for Java and .NET teams

Test automation, built like good software.

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.

  • 15+ years in software development
  • Java · Kotlin · C#/.NET
  • Industrial & enterprise systems
  • ISTQB certified
  • Remote across Europe
Technical performance
“technically sound, independent, open, reflective”
Remote collaboration
“easy to reach, frictionless”
Engage again?
“Definitely.”
Head of Platform Engineering, Manufacturer of industrial energy technology
signed interim project review · 11/2026, translated from German

Typical situations

Do any of these sound familiar? This is where I come in.

The framework grew – it wasn't designed.

Every change takes longer than it should, and nobody dares to touch the core structure any more.

Red tests nobody believes.

Flaky tests get ignored or re-run again and again. Trust in the pipeline erodes.

Maintenance eats the automation.

Much of the time goes into fixing existing tests instead of adding new coverage.

Tests run beside the pipeline, not in it.

Results arrive too late or have to be collected by hand.

Everything depends on one person.

When the framework specialist is away or leaves, test automation stalls.

Distributed teams, different standards.

Teams in several locations automate in different ways. Results are hard to compare.

Services

Three focus areas plus classic development – always aiming for your team to carry on independently.

Framework rescue & modernisation

Typical situation

An existing framework has become unstable, slow or hard to maintain.

What I do

  • Review of architecture, stability and run times
  • Removing flaky tests and technical debt
  • Migration, e.g. Selenium → Playwright, including C# → Java
  • Step by step, without stopping delivery

What you get

A framework your team trusts again and can extend with reasonable effort.

Test platform engineering

Typical situation

Test automation needs to be built from scratch or set up anew.

What I do

  • Framework architecture and reusable components
  • UI, API, integration and end-to-end tests – including hardware-dependent systems
  • Reporting and analysis of test results
  • CI/CD integration, Docker, Kubernetes, Azure

What you get

A test platform that is developed, versioned and operated like product code.

Developer enablement

Typical situation

Your team – or several teams in different locations – should own test automation.

What I do

  • Standards, conventions and architecture principles
  • Onboarding, including internationally distributed teams
  • Code reviews, pair programming, workshops
  • Documentation and structured handover

What you get

Less dependency on individuals – including on me.

Software engineering

Typical situation

You need experienced development capacity in Java, Kotlin or .NET.

What I do

  • Backend and API development (Java, Spring, Kotlin, ASP.NET Core)
  • Full stack with Angular and TypeScript
  • ERP/CRM integration via REST and SOAP
  • Testability built in from the start

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 →

What makes QUALENDIX different

  • Test automation is software engineering. I come from development. My frameworks are built with clean architecture, code reviews and CI/CD – not as a collection of scripts.
  • More than tests: the platform around them. Besides tests, I build reporting and analytics platforms, API test frameworks, backend components and integrations.
  • Experience with complex systems. Industrial software and hardware systems in the energy sector, safety-critical railway technology, enterprise integration with ERP and CRM.
  • Across languages and tools. Java, Kotlin and C#/.NET – including migrations between languages and tools.
  • Handover is part of the job. Your team should run the result on its own, across locations and languages. And you work directly with me, not with junior consultants.

Project experience

Selected projects, described by situation, solution and result. I'm happy to name clients in a personal conversation.

Energy technology · since 2024

A new framework generation for industrial software and hardware systems

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

BDD test automation for safety-critical signalling systems

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

Integration and automation of business processes

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.”

Deputy Head of Development, Manufacturer of safety-critical railway signalling technology
asked whether they would work with me again · reference 12/2023, translated from German

Migrating from Selenium to Playwright

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.

  • Inventory and prioritisation of the test suite
  • Target architecture with reusable components
  • Parallel operation instead of a big bang – your coverage stays in place
  • Integration with Jenkins, GitLab CI or Azure DevOps
  • Handover, documentation and onboarding of your team

Approach

  1. AssessFramework assessment: where does your test automation stand, where are the risks and levers?
  2. DesignTarget architecture, technology decision and prioritised roadmap.
  3. BuildBuild or modernisation together with your team, integrated into your pipeline.
  4. Hand overStandards, documentation and onboarding – your team runs the framework on its own.

Where is your test automation stuck?

Briefly describe your situation – you'll get an honest first assessment, even if I'm not the right fit for your topic.

Describe your situation

Technologies

Languages

  • Java
  • Kotlin
  • C# / .NET
  • TypeScript
  • Python

Test automation

  • Playwright
  • Selenium
  • JUnit
  • MSTest
  • Cucumber / BDD
  • REST API testing

Frameworks

  • Spring / Spring Boot
  • ASP.NET Core
  • Angular
  • OSGi

CI/CD & cloud

  • GitLab CI/CD
  • Jenkins
  • Azure DevOps
  • Docker
  • Kubernetes
  • Microsoft Azure
Portrait of Felix Bliedung

Profile

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.

Company
QUALENDIX DEVELOPMENT LTD
Based in
Cyprus (EU), VAT/VIES registered
Insurance
Professional liability
Certification
ISTQB Certified Tester Foundation Level
Delivery
Remote; on-site by arrangement
Engagement
Direct or via partners and agencies

Frequently asked questions

How is this different from classic QA consulting?

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.

Will I work with you directly?

Yes. QUALENDIX is deliberately small: you work directly with me, without being handed on to other consultants.

Do you work fully remotely?

Usually, yes. Planned on-site visits, for example for workshops or kick-offs, are possible by arrangement.

How does invoicing with a Cypriot company work?

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.

How long does a Selenium to Playwright migration take?

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.

Do you work through agencies or as a subcontractor?

Yes, working through staffing partners, software houses and IT service providers is straightforward.

Contact

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