When errors occur in production, they must be laboriously fixed, validated and redeployed. All these steps take time – and time costs money. Finding errors earlier can reduce these costs by 80%.
Test Automation
Test automation: Reduce costs, increase profits
Faulty software costs you customers, time, and money. Use test automation now: speed up development, save on rework, and delight your users.
Automation is not just a corporate topic. It can give you a decisive competitive advantage, especially in small and medium-sized businesses: Others are not doing it or are not able to.
Why test automation is a good idea for you too
Every bug that reaches your customers costs you money. While you test manually (or skip testing altogether), you lose potential customers every day to competitors with bug-free software.
- 88% of users delete apps after their first bug experience
- Manual tests are the first to be canceled when time is tight.
- A single critical mistake can ruin your reputation
- Your developers spend 40% of their time on bug fixes instead of new features.
Don't you agree that software should work perfectly?
What are the specific Benefits of Test Automation?
You can look forward to the following benefits:
More Profit from Revenue
Fewer User facing Bugs
Every bug that a user encounters not only causes inconvenience: it directly damages the reputation of the product. Who would entrust all their money to software that gives the impression that it miscalculates?
Faster Deployments
Instead of slowing things down, test automation has the opposite effect: when implemented intelligently, it ensures that virtually no rework is required for deployments because it is available at all times. Instead of performing one-off manual testing at release and missing the deadline with an unpredictable list of errors, "finished" really means finished. That's because the test has already been performed – several times.
Reliable Deadlines
Since the quality status is known at all times, it can be used for planning purposes: Instead of having to work a weekend shift at the last minute, it is already clear during development what rework still needs to be done. This provides planning reliability. And speed.
Happy Investors
Relying on a product is one thing. With test automation, you can demonstrate the reliability of a product in a comprehensible way. This is a quality feature when it comes to raising external capital.
Max – Bug Sniper
I am Max, the Bug Sniper. For companies every size from Start-Ups to Global Corporation, I have been testing software for over 10 years. I know both worlds: The depth of processes in Finance and Automotive and the speed of Start-Ups. I am an entrepreneur – and I work as flexibly as you need me to:
- For 1 ticket that is burning RIGHT NOW – To get rid of stress immediately.
- For 3 months, every 2 weeks – To know that a challenge has been completed sustainably and to a high standard.
- For a permanently efficient solution – saving you time, money, and stress.
Let's find out NOW what will help you the most!
My Track Record
A selection of projects I completed successfully:
LichtBlick SE From 0 QA to almost 0 Bugs in Production
Assignment: Please introduce testing to our IT department.
Procedure: Working closely together with the teams, I introduced different procedures on how to integrate tests into their way of working.
Result: As everybody could proceed like how it fits best for them, processes were accepted easily which reduced the bugs in production to almost 0.
BRITA SE Build Time reduced to half, increased development speed
Assignment: Help us with our Automation.
Procedure: Together with the customers team, we put the code base to a healthy state. For this, I introduced new standards, refactored plain JavaScript to TypeScript and parallelized the tests.
Result: Not only the tests provided more and more helpful data for all stakeholders. The Build Time was cut in half which sustainably increased acceptance for the tests and the development of new features.
StarFinanz From Problem Child to Quality Managements Favorite
Assignment: Help us with Testing & Compliance
Procedure: Looking at Process & Requirements as whole I found duplicates in documentation and way of working. As well I connected open ends and made the process sleek. Now, every task has to be done only once.
Result: By reducing duplicates, with every quarterly release the client saves a lot of time. Also, bugs are found earlier. The customers Quality Management department is happy as well: Complaints have dropped to almost 0.
Feedback for my Results
Pierre Wilken
Founder & CEO
@Karrierehero
04/2025
Project Qualitätssicherung der Bildungsangebote
"Seitdem Max uns als externer Berater für die Qualitätssicherung unterstützt, ist nichts mehr "mal eben durchgewunken". Und das ist gut so."
Max ist einer dieser Menschen, bei denen man sich fragt: Wie haben wir eigentlich vorher ohne ihn gearbeitet?
Seitdem Max uns als externer Berater für die Qualitätssicherung unterstützt, ist nichts mehr "mal eben durchgewunken". Und das ist gut so. Denn was Max mitbringt, ist ein unfassbarer Blick fürs Detail, eine analytische Tiefe und diese schonungslose Ehrlichkeit, die man manchmal braucht – auch wenn sie kurz piekst.
Er arbeitet sich mit beeindruckender Sorgfalt durch alles, was wir aufbereiten, stellt kluge Fragen und bringt Perspektiven rein, auf die wir von allein nicht gekommen wären. Und das Wichtigste: Er verliert nie den Blick für das, was Kund:innen wirklich brauchen. Max denkt nicht aus Anbieter-, sondern aus Nutzer:innen-Sicht. Und genau deshalb ist sein Feedback so wertvoll.
Dazu kommt: Max ist einfach ein richtig guter Mensch. Wahnsinnig engagiert, zuverlässig, loyal – und immer bereit, noch eine Runde mitzudenken, wenn es drauf ankommt. Mit ihm an der Seite fühlt es sich nicht nach "externer Berater", sondern nach echter Zusammenarbeit auf Augenhöhe an.
Wenn du jemanden brauchst, der mitdenkt, mitfühlt und mit anpackt – arbeite mit Max. Punkt.
Danke dir, Max – für deine Klarheit, deine Genauigkeit und deinen unermüdlichen Einsatz.
Du machst unsere Arbeit besser. Und mich tatsächlich auch!
Felix Dziekan
Freelance Software-Entwickler
@Selbstständig
02/2025
Project MyMediaPlanner
"Ich habe jetzt eine volle To-do-Liste, die einen massiven Mehrwert fĂĽr meine User bringen wird."
Max nervt wie sau - Und das ist gut so!
Denn genau das ist sein Job! Ich hatte mit Max eine 90 Min QA Session für mein neues Tool, welches sich im Betatest befindet. Vor unserer Session war ich überzeugt davon, dass es zwar ein paar Kleinigkeiten geben wird, aber sicher werden wir die 90 Minuten nicht voll kriegen. Boy oh Boy lag ich falsch! Max hat Dinge aufgedeckt, die mir als Entwickler schon gar nicht aufgefallen sind und auch nie aufgefallen wären. Nicht nur hat er das Tool aus UX und Anwendersicht auseinander genommen, ihm sind sogar die kleinsten Pixelfehler in der Navigation aufgefallen.
Ich habe jetzt eine volle To-do-Liste, die einen massiven Mehrwert für meine User bringen wird und wenn die umgesetzt ist, hole ich mir die nächste Ladung bei ihm ab!
Nicolas Kopp
Awarded Freelancer & CTO
@digital essence GmbH
02/2025
Project Lane (App)
"[Max] sieht Dinge, die man selbst schon gar nicht mehr wahrnimmt."
Max hat unsere Aktien-App Lane in einem 90-minütigen Sparring getestet – und er hat nicht einfach nur freundlich über den Bildschirm geschaut. Nein, Max hat hinter die Kulissen geblickt, Dinge hinterfragt, Begriffe auseinandergenommen und uns mit gezielten, treffsicheren Analysen den Spiegel vorgehalten. In einem Tempo, das uns manchmal kurz die Augenbrauen hochziehen ließ.
Seine größte Stärke? Er sieht Dinge, die man selbst schon gar nicht mehr wahrnimmt. Dieses „Da habt ihr doch sicher bewusst entschieden, das so zu machen?“ – gefolgt von einem Moment der Stille, in dem man realisiert, dass man sich nie wirklich Gedanken darüber gemacht hat. Und genau da setzt er an. Ob es um unklare Begriffe, unglückliche Nutzerführung oder winzige Details geht, die aus Sicht der User den Unterschied zwischen „Verstanden!“ und „Häh?“ machen – Max findet sie. Und wenn man denkt, jetzt müsste doch wirklich alles wasserdicht sein, dann findet er noch eine Kleinigkeit.
Natürlich tut Veränderung manchmal weh. Aber wie heißt es so schön? Wo gehobelt wird, fallen Späne – und Max ist nicht der Typ, der davor zurückschreckt. Allerdings hat er die seltene Fähigkeit, nicht nur Probleme zu benennen, sondern gleich pragmatische, realisierbare Lösungen vorzuschlagen. Kein nebulöses „Man könnte mal überlegen…“, sondern klare, durchdachte Ideen, die sich direkt umsetzen lassen.
Wer also nicht nur ein freundliches Abnicken, sondern ehrliches, konstruktives Feedback sucht – gewürzt mit einer guten Portion Scharfsinn und Lösungsorientierung – sollte Max ins Boot holen. Ein echter Mehrwert für jedes Produktteam, das nicht in der eigenen Betriebsblindheit stecken bleiben will. Klare Empfehlung!
Benedikt Hofmann
Teamlead IoT, Web & Mobile
@BRITA SE
09/2023 – 07/2024
Project IoT Customer Portal
"Einfach ein toller Mensch - und damit eine technische und menschliche Bereicherung fĂĽr jedes Unternehmen."
Kurz und knapp: absolute Empfehlung!
Max war fĂĽr uns von September 2023 bis Juli 2024 im Projekteinsatz und hat fĂĽr uns als externer Dienstleister die Testautomatisierung auf verschiedenen Ebenen (Single Page-, API-, End-2-End-Testing) umgesetzt.
Dabei hat sich Max unfassbar schnell in das bestehende Framework eingearbeitet, Arbeitspakete direkt und schnell identifiziert und umgesetzt, Optimierungen erkannt und den Entwickler*innen gemeldet, und wirklich hilfreiche Insights fĂĽr unsere Plattform erzeugt.
Das Ganze macht Max auf seine typisch sympathische und offene Art - einfach ein toller Mensch - und damit eine technische und menschliche Bereicherung fĂĽr jedes Unternehmen.
Oliver Oliv
Product Owner
@Total Energies
09/2022 – 03/2023
Project Customer Portal
"Er hat sich nicht nur auf das reine Testen beschränkt, sondern daran mitgearbeitet, den Entwicklungsprozess hinsichtlich Qualitätssicherung zu gestalten und voranzubring[e]n."
Max hat 2022 im Bereich Charging Solutions in der Entwicklung eines Kundeportals als Consultant mit Schwerpunkt Software-QA unterstĂĽtzt und dabei den Release des MVPs erfolgreich begleitet.
Durch seine technische Expertise konnte er sehr eng mit den Entwickler:innen zusammenarbeiten, sodass das gesamte Team von seinem umfangreichen Fachwissen profitierten konnte.
Er hat sich nicht nur auf das reine Testen beschränkt, sondern daran mitgearbeitet, den Entwicklungsprozess hinsichtlich Qualitätssicherung zu gestalten und voranzubringn. Er hat sowohl die Product Owner bei der Erstellung der Anforderungen unterstützt und diese hinsichtlich Spezifikationslücken und Sinnhaftigkeit geprüft.
Speziell seine selbständige Arbeitsweise und seine Kommunikation mit dem Team ist besonders positiv hervorzuheben.
Des Weiteren schaffte er groĂźen Mehrwert, indem er seine Kenntnisse im Bereich Cybersecurity direkt beim Testen sinnvoll einsetzte und wir dadurch erfolgreich einen externen Pentest bestehen konnten.
Lyubomir Mihaylov
(external) Agile Coach
@Mercedes-Benz.io
11/2021 – 06/2022
Project Product Catalogue
"During day-to-day challenges, Max was always there to provide guidance and support not only with technical expertise, but also as a mentor to various colleagues"
Max's experience and expertise that I saw while working together at Mercedes Benz IO was invaluable and very thorough. Max showcased great resilience and methodical approach to work and dealing with ambiguity. During day-to-day challenges, Max was always there to provide guidance and support not only with technical expertise, but also as a mentor to various colleagues regarding specific QA related topics and Agility in general. Max's understanding around highly complex issues was very well appreciated by peers and his suggestions and improvements were always taken into consideration. Max will be great in environments which are complex that provide lots of challenges and that require analytical approach in which he takes a leading role and leads by example.
Artjom Petersen
Department Lead Mobile
@StarFinanz
04/2019 – 08/2019
Project yomo App
"Trotz des sehr engen Zeitplans [stellte er] eine hohe Arbeitsbereitschaft und Organisationsfähigkeit unter Beweis."
Max hat uns im Bereich Mobile Services der Star Finanz von April bis August 2019 als Software-Qualitätssicherer unterstützt. Durch seine jederzeit sicheren Kenntnisse konnte er sich dabei besonders schnell in das komplexe Gefüge der Banking-App einfinden. Während der Testphase des von ihm verantworteten Releases stellte er trotz des sehr engen Zeitplans eine hohe Arbeitsbereitschaft und Organisationsfähigkeit unter Beweis.
Rainer Gibbert
Department Lead B2C
@StarFinanz
09/2022 – 03/2023
Project StarMoney Windows
"Max hat [...] das Team dabei unterstĂĽtzt und beraten, die Test-Methoden zu optimieren und voranzutreiben."
Max hat uns im Privatkundenbereich der Star Finanz von September 2018 bis März 2019 als Software-Tester unterstützt und den Release von StarMoney 12 mit vorbereitet und begleitet. Dabei hat sich Max sehr gut in das bestehende Team eingefunden und sein Wissen proaktiv eingebracht. Max hat sich dabei nicht nur als reiner Tester gesehen, sondern hat das Team dabei unterstützt und beraten, die Test-Methoden zu optimieren und voranzutreiben. Max war stets sehr freundlich, zuvorkommend und hilfsbereit. Er war immer daran interessiert, Feedback zu sich und seiner Arbeitsweise zu bekommen, um seine Dienstleistung weiter zu verbessern.
What is Test Automation?
Test automation refers to the use of software tools to carry out tests without manual intervention. This enables faster and more consistent validation of software functions. Automated tests can be used in different phases of the software development cycle and are particularly helpful for repeatable test scenarios.
Kinds of Automated Tests (Selection)
- Static Code Analysis or Linting: The code is regularly analyzed by tools using various rules. This can range from rules for bracket replacement to automatic systems that check dependencies for known vulnerabilities.
- Unit Tests: Checking individual code units at function level.
- Integration Tests: Testing the interaction between different components.
- API Test: Testing the interface of individual program components. Strictly speaking, this is a component test or, depending on the perspective, even an end-to-end test.
- End-to-End Tests: simulation of an entire workflow from the user's perspective.
- Performance Tests: Evaluation of software performance under different load conditions.
Why is Test Automation Important?
Test automation not only saves valuable time - a resource that cannot be scaled at will. Test automation also enables flexible testing at any time, i.e. much more often than would be possible in a manual test.
1. Increased Efficiency and Speed
Automated tests can be carried out around the clock and save time compared to manual tests.
2. Improved Test Coverage
Automation allows more tests to be carried out in less time, enabling greater coverage.
3. Faster Error Detection
Errors are found earlier in the development process, which reduces rectification costs.
4. Consistency and Repeatability
Automated tests always deliver the same results and minimize human error.
5. Support and Acceleration of the Development Process
Not only do automated tests help to dramatically shorten the release cycle, they also create the freedom to “just run all the tests for a moment” - the possibility of receiving support from a quality assurance expert who is neither tired, slow nor corruptible, even during ongoing development.
The Procedure of Automating Tests
To ensure that the test automation project is a success, the following steps can provide orientation. I am of course happy to support you with the project.
1. Selection of the Test Cases to be Automated
Recurring tasks should be automated, which includes not only the testing itself, but also the setup and data enrichment of the test environment. With careful planning, the most important test cases to be automated are targeted, which on the one hand brings immediate relief and on the other hand increases acceptance in the team through feedback effects.
2. Selection of the right Test Automation Tools
The choice of tools is at least as important as the choice of test cases. If the aim is to work closely with the specialist department, Cucumber / Gherkin can provide useful support. If the test team tends to work autonomously, a solution that does not abstract the technical view should be preferred in order to increase maintainability. Tools such as Playwright for user interfaces or Appium for smartphone apps can be used, but also XCTest, for example, if it is purely about the quality assurance of an iOS app. In any case, the decision should not be made lightly based on an affinity for a particular framework, but should always keep the big picture in mind.
3. Development and Implementation of Test Cases
The development of robust and maintainable tests describes the main part of the work in the implementation. It should be constantly kept in mind which elements can be reused sensibly in order to limit the duplication of code to a reasonable extent. The Page Object Model (POM) can be a help here because it encapsulates the logic of “finding” UI elements from the actual code and thus makes them maintainable in a central location.
4. Integration into the CI/CD Pipeline
The (optional) integration of test automation into the build process ensures that the tests are carried out with every change and that errors are detected at an early stage. The decision as to whether the test step is a mandatory part of the build, i.e. whether a failing test stops the build itself, must be made on a case-by-case basis and from team to team. If acceptance is not yet given, it can make sense to make the test step optional at first to avoid frustration and resentment.
5. Maintenance and Optimization of the Tests
Automated tests must be regularly reviewed and adapted to keep pace with software development.
Best Practices for Successful Test Automation
In my many years of working with a wide variety of automation solutions, I have found a couple of best practices. Some of them are:
Focus on the Right Tests
Not every test should be automated. Focus on tests that are often repeated or cover critical functionalities.
Use of Page Object Models (POM) for UI Tests
This architecture facilitates the maintenance and reusability of test scripts.
Test Data Management
Safe, consistent and realistic test data ensures reliable test results.
Combination of Manual and Automated Tests
Automation supplements, but does not replace all manual tests. Exploratory tests should continue to be carried out manually, because detecting “pixel errors”, for example, is not one of the strengths of test automation. Enabling these effects by machine is possible, but is very unfavorable in terms of maintenance in relation to the costs.
Continuous Maintenance of the Test Suites
Test automation is not a one-off process - regular updates and adjustments are required.
Challenges in Test Automation
High Initial Implementation Effort
Problem: Automation initially requires time and resources.
Solution: Gradual introduction and prioritization of the most important tests.
Maintenance Effort for Test Cases
Problem: Changes to the software can invalidate tests.
Solution: Use of robust frameworks and regular adaptation of the tests.
False Test Results (False Positives/Negatives)
Problem: Automated tests can deliver unexpected results.
Solution: Regular validation and improvement of the tests.
Complexity (especially) for UI tests
Problem: Changes to the front end can make tests unusable.
Solution: Use of stable selectors and POM methodology. Joint responsibility of frontend and QA team for the page objects.
Flakiness
Problem: Tests fail “sometimes”, but work most of the time.
Solution: This is the biggest problem of test automation as a concept, so there is no trivial answer. Speaking error messages, “screenshot on failure” and a debugger-compatible solution are essential.
Conclusion
Well-designed test automation does not eliminate all manual effort – if you are striving for a 100% solution. Nevertheless, it can be a huge help and easily save 95% of manual effort. It ensures a structured implementation that is always the same. It minimises the likelihood of errors being brought into production. For investors, it is also a sign of quality. Test automation should therefore be part of every development strategy. Getting started is quick and easy: All we need is one hour to discuss the architecture, a little time for me to implement it, and within a week the basic suite is ready for handover with a proof of concept. In the meantime, I don't want to acquire ownership of the code – I am not another dependency, I am a booster.
Frequently Asked Questions
How does Test Automation work?
Test automation works on the principle of having a software application perform a use case using software. This test is specifically designed to recognise that the correct result follows an input.
Which kinds of Test Automation are there?
They can be roughly divided into unit tests, component tests, system tests and acceptance tests. Unit tests check the smallest functions, components and individual parts of the software, system tests check the system as a whole, and acceptance tests check the system against the specifications.
Is test automation really worth the money?
Yes - on the one hand because manual effort is saved and the tests can be carried out significantly more often thanks to automation. And will.
How do you provide good Tests?
This usually depends on the test level: While it is important in automated E2E testing to generate as much coverage as possible with minimal effort, tests at lower levels also help with debugging and are therefore more granular.
How long does it take, until Test Automation is cost neutral?
As a rule, after just three months the point is reached where automation is more useful than it has cost up to that point, because so much manual effort is saved and the tests are carried out many times more often.
Where is Test Automation limited?
It's quite clear: when it comes to a sense of proportion and user interaction. This is target group-specific and cannot practically be checked by a machine.
What technologies for Test Automation are out there?
There are powerful tools for automating tests of all kinds in every programming language, ranging from unit tests to the actual simulation of user behavior on the user interface.
Which Maintenance Effort does a Test Automation have?
In addition to the test cases, which have to be adapted to the current development, the automation framework itself also generates maintenance work because it has to be kept up to date. During operation, however, these costs are significantly lower than those of manual testing.