QA & Test Automation

QA and test automation that keeps releases safe

We test web apps, mobile apps and APIs by hand and with automated tests, for a single release or as an ongoing QA team. You see what was tested, what failed and what it means for the release before your users do.

Start a project
See our work

Organisations we've built for

  • MeQrez General Hospital
  • Space Science and Geospatial Institute
  • Ahadu Bank

Best for

When QA and test automation are the right move

If one of these sounds like your releases, we can help.

No safety net

Every release is a gamble, and bugs show up in production first.

Automated tests on the critical user journeys, run in the pipeline on every change.

Manual regression

Your team spends days clicking through the app before each release.

The repeated checks automated, so people spend their time testing what's new.

Many devices

The app works on your phone, but not on your customers' phones.

Tests across the devices, browsers and operating systems your users actually have.

Evidence for audits

Regulated clients or auditors ask how the software was tested.

Test plans, results and links to the requirements, kept as evidence for every release.

What you get

What our QA work covers

Testing planned around the risks of your product, not around a number of test cases.

Manual testing

Exploratory, functional and usability testing by testers who know where software tends to break.

Test automation

UI, API and mobile tests in Cypress, Selenium or Appium, running in your pipeline.

Performance testing

Load and stress tests that show how the system behaves before your busiest day does.

QA as a service

An ongoing QA team for your releases, from one tester to a full team.

Every QA engagement includes

A test plan built around your risks

Tests in your repository and pipeline

A clear report for every release

Synthetic or anonymised test data

How we deliver

From the first test plan to releases you trust

The same three steps as every project we run, starting with what would hurt most if it broke.

01

Plan

We learn the product, rank the risks with you and agree what to test by hand, what to automate and what we won't test.

02

Thin slice

The most critical user journey covered first, by hand and automated, and running in your pipeline early. Then coverage grows, with results every week.

03

Launch and handover

Tests, test data and documentation handed over, so your team can keep them running, or we stay on as your QA team.

How we work

Security and data

Test data that protects your users

Testing needs realistic data. It doesn't need your customers' personal data.

Synthetic test data.

Test data that's synthetic or anonymised. Production personal data is never copied.

Test environments only.

We test in staging and test environments, with the access the work needs, under a data processing agreement. Every engineer can sign an NDA if you want one.

Security in the test plan.

Checks such as who can see which data are part of the functional tests. Deeper testing is our application security work.

How we protect your data

Sectors and technologies

Where we've tested, and what we test with

Sectors

Our engineering team has built and tested systems for hospitals, banks and cooperatives, where a wrong figure or a lost record isn't an option.

Healthcare

Financial services

Logistics & mobility

Public sector & geospatial

Technologies

The tools we use most, on the platforms your users have. We work with yours if you already have them.

Cypress

Selenium

Appium

Web

iOS

Android

APIs

FAQ

Questions about QA and test automation

A test plan based on your risks, automated tests that run on every change, manual and exploratory testing for what's new, and a short report after each release. It can cover web apps, mobile apps and APIs.

Both, for different jobs. Automated tests check what must never break, on every change. People test what's new, how it feels to use and the cases nobody thought of. The test plan says which is which.

Mostly Cypress and Selenium for web apps, Appium for mobile apps, and API tests in the same pipeline. If you already have tools and tests, we build on them.

Yes. Most QA work starts on existing software. We learn the product, read the requirements and talk to your team, then start with the riskiest user journey.

The devices and browsers your users have, agreed from your analytics. Where a device lab or a cloud device service is needed, the proposal says which one.

Yes. We check against WCAG 2.1 AA with automated checks and manual testing, including keyboard use and screen readers. That helps if your service falls under Germany's BFSG, which has applied to many consumer services since 28 June 2025.

A short report: what was tested, what passed, what failed and how serious it is, so you can decide whether to release with the facts in front of you.

Test data is synthetic or anonymised, and production personal data is never copied into a test system. We work under a data processing agreement, and every engineer can sign an NDA if you want one.

Yes. Testers join your planning and demos, and bugs go into your tracker with the steps to reproduce them. Our team lead plans and runs our testers' work.

A test plan based on your risks, automated tests that run on every change, manual and exploratory testing for what's new, and a short report after each release. It can cover web apps, mobile apps and APIs.

Both, for different jobs. Automated tests check what must never break, on every change. People test what's new, how it feels to use and the cases nobody thought of. The test plan says which is which.

Mostly Cypress and Selenium for web apps, Appium for mobile apps, and API tests in the same pipeline. If you already have tools and tests, we build on them.

Yes. Most QA work starts on existing software. We learn the product, read the requirements and talk to your team, then start with the riskiest user journey.

The devices and browsers your users have, agreed from your analytics. Where a device lab or a cloud device service is needed, the proposal says which one.

Yes. We check against WCAG 2.1 AA with automated checks and manual testing, including keyboard use and screen readers. That helps if your service falls under Germany's BFSG, which has applied to many consumer services since 28 June 2025.

A short report: what was tested, what passed, what failed and how serious it is, so you can decide whether to release with the facts in front of you.

Test data is synthetic or anonymised, and production personal data is never copied into a test system. We work under a data processing agreement, and every engineer can sign an NDA if you want one.

Yes. Testers join your planning and demos, and bugs go into your tracker with the steps to reproduce them. Our team lead plans and runs our testers' work.

A test plan based on your risks, automated tests that run on every change, manual and exploratory testing for what's new, and a short report after each release. It can cover web apps, mobile apps and APIs.

Both, for different jobs. Automated tests check what must never break, on every change. People test what's new, how it feels to use and the cases nobody thought of. The test plan says which is which.

Mostly Cypress and Selenium for web apps, Appium for mobile apps, and API tests in the same pipeline. If you already have tools and tests, we build on them.

Yes. Most QA work starts on existing software. We learn the product, read the requirements and talk to your team, then start with the riskiest user journey.

The devices and browsers your users have, agreed from your analytics. Where a device lab or a cloud device service is needed, the proposal says which one.

Yes. We check against WCAG 2.1 AA with automated checks and manual testing, including keyboard use and screen readers. That helps if your service falls under Germany's BFSG, which has applied to many consumer services since 28 June 2025.

A short report: what was tested, what passed, what failed and how serious it is, so you can decide whether to release with the facts in front of you.

Test data is synthetic or anonymised, and production personal data is never copied into a test system. We work under a data processing agreement, and every engineer can sign an NDA if you want one.

Yes. Testers join your planning and demos, and bugs go into your tracker with the steps to reproduce them. Our team lead plans and runs our testers' work.

Related services

Often combined with

Rescue & run

DevOps & Managed Support

Tests in a pipeline that deploys and monitors, so a failing test stops a bad release.

Quality & security

Application Security Testing

Penetration tests for web, mobile and APIs, for the weaknesses functional tests don't look for.

Rescue & run

Codebase Recovery & Stabilisation

If the code has no tests at all, we stabilise it first, then cover it step by step.

Have a project in mind?

We reply within one working day.

FlightLabs is a Berlin-based software engineering company that builds, tests, secures and runs production software and AI for European companies, with its engineering team in Addis Ababa, 1–2 hours from Central European Time.

hello@flightlabs.ioBerlin, GermanyEngineering team: Addis Ababa, Ethiopia
LinkedIn (opens in a new tab)

In partnership with eTech S.C.