Services
Quality assurance & test automation
Most small software companies have no independent QA. We do - and that is why our systems keep running after handover.
When we are the right fit - and when we are not
Where we carry weight - and where we do not.
A fit when …
- A test strategy is missing or has become unusable over the years.
- Test automation should be built up, not just individual tests written.
- There are regulatory requirements for test documentation and traceability.
- Distributed systems, streaming or time series data need validating.
Not a fit when …
- What is wanted is a pure clicking resource for manual regression runs.
- Tests are meant to retrofit quality that is missing from the design.
- There is no willingness to make tests a binding merge gate.
- Below 10 person-days our ramp-up effort does not pay off for you.
The levels at a glance
| Level | Services |
|---|---|
| Test strategy | Test design, requirements engineering, acceptance criteria, test management |
| Manual testing | Black-box and white-box tests, exploratory testing, system integration tests, retesting of fixes |
| Test automation | Unit tests (xUnit, Karma/Jasmine), GUI automation (Squish, Selenium), E2E tests (Cypress), integration tests against real services and databases (WebApplicationFactory, Testcontainers) |
| Process anchoring | Test-driven development as team standard, mandatory CI/CD quality gates, continuous increase in coverage and degree of automation |
| Specialist testing | GDPR, accessibility and usability testing, non-functional tests, validation of streaming and time series data |
| Documentation | Test case management, test logs and reports, release documentation, manuals, context help, screencasts |
| Test environments | Reproducible environments via Docker and Testcontainers, VMware, Proxmox, VirtualBox; synthetic test data |
Why QA is a role here, not a phase
In most companies of this size, developers test their own code - with the familiar blind spot - or the client takes on acceptance. Here, an ISTQB-certified test manager owns quality assurance from the management level. That shifts the priorities: tests are a merge gate, not an afterthought; test documentation is part of the product, not decoration.
This explicitly includes agent-generated code. Every change goes through build, unit, integration and E2E tests plus static analysis. Nothing bypasses the pipeline.
Approach & collaboration models
Most common entry point: an assessment of the existing test landscape with prioritised measures. Then building or repairing the automation, either by us or alongside your team.
Technologies
Project reports from this field
EcoPulse
An event-driven microservice platform that consolidates inverters, storage, wallboxes and meters into a shared time series base and derives load decisions from it. Energy · IIoT · e-mobilityPhonalisa
A complete IP telephony platform we have owned architecturally since our founding in 2009, developing, testing and documenting it. TelecommunicationsCondition monitoring migration
Migration of a mature C++ backend to .NET Core with Entity Framework, including a redesign of the data access layer. Industrial automationMedical laser system
Development, testing and documentation of the planning and treatment interfaces of a laser system in an approval-relevant setting. Medical technology · regulatedTax software
Further development and quality assurance over several years: legislative updates, form logic, accessibility and GDPR. Public administration · financeTypical project size
What a project costs with us.
Day rate €480-960 depending on the type of engagement
Below 10 person-days our ramp-up effort does not pay off for you. An assessment of your existing test landscape works as a short entry point.
Frequently asked questions
What does end-to-end test mean here?
A test against a genuinely running API including a real database via Testcontainers, covering authorisation and error paths. Not against mocks: a mock confirms your own assumption, a real database contradicts it.
Will you work inside our existing test estate?
Yes. A common entry point is taking over and repairing a mature test suite - stabilising flaky tests, cutting runtime, closing coverage gaps, then expanding.
How do you handle accessibility and GDPR?
As distinct test types. In the tax software of a state finance authority, accessibility and GDPR testing were an integral part of system testing, not an add-on.
Contact
Your contact
Quality assurance, test management & company management