From the PMC teamDevelopment projects start in 2027. Plan yours now to secure an early start.

Test automation

Tests that run on every change, so your users do not have to.

We write automated end-to-end, API and load tests, run them in your pipeline and report every result, so a release no longer depends on someone clicking through the application.

  • Fast to deliver
  • Built to last
  • Secure from day one
11+years of building software for finance, IT and project teamsAbout the team
Test automation

Our test automation services

End-to-end, API, load and acceptance tests that run on every change, so a green pipeline means the application works.

End-to-end testing

Real browsers walk through your most important journeys on every change.

Discuss this service

What we cover: Every layer, from unit tests to end-to-end runs in the browser and on mobile, wired into your pipeline. PMC itself is tested this way, with test runs that play several users at once.

The team behind PMC, trusted by
  • BNP Paribas
  • Allianz
  • Hexagon
  • Hewlett Packard Enterprise
  • Enapter
Solutions

Test automation we set up

  • A safety net for releases

    The main journeys of your application are tested before every release.

  • Several users at once

    Tests sign in several users in parallel and check that each sees the other's changes.

  • Before a modernisation

    Tests describe what an old application does, before anyone changes it.

  • Acceptance tests

    Test cases written with your departments, then run automatically from that day on.

Every release still needs a week of manual testing?

Show us the journeys your testers click through by hand. We tell you which ones to automate first and how long it takes.

Plan your test suite
A worked example

How a project like this runs.

Example

A safety net before a modernisation

The situation

An internal application is about to be rebuilt, but nobody can say exactly what it does in every case.

What we do
  1. We choose the journeys that would hurt most if they broke, with the people who use them.

  2. Playwright tests walk through each journey in a real browser, with realistic test data.

  3. API tests check the answers other systems rely on.

  4. The tests run on every change, and the report goes to the team.

The result

The rebuild can be checked against the old behaviour at every step.

An illustrative example of the way we work, not a named customer.

AI inside

AI in testing

To write and maintain tests faster, never to replace the check.

  • Test case suggestions
  • Test data generation
  • Flaky test analysis
  • Testing AI assistants
  • Visual change checks
  • Readable test reports
  • Failure causes summarised
  • Coverage gaps highlighted
  • Answer quality measured
Why it pays

Why automate your tests

01

Main journeys checked on every change

Today
Before every release, someone clicks through the application for hours.
With it in place
The main journeys tested automatically on every change, in several browsers.
Tests you can trust

A green run that means something.

Tests only help when the team believes them.

Stable, not flaky
Tests that fail at random are fixed or removed, so a red run always means a real problem.
Realistic data, no personal data
Test data mirrors real cases without copying personal data from production.
Fast feedback
The checks that matter most run first, so developers know within minutes.
Owned by your team
Tests live in your repository and are written so your developers can extend them.
What you receive

Everything you need to own the result.

  • End-to-end, API and load tests in your repository
  • Test data that mirrors real cases without personal data
  • The tests wired into your pipeline
  • A report with screenshots and recordings for every run
  • A short guide for your developers to add new tests

Is it right for you?

A good fit when
  • Applications checked by hand before every release
  • A modernisation or a framework upgrade ahead
  • Several user roles, or several users working at the same time
Not the right fit when
  • A prototype that will be thrown away in a few weeks
Speed, quality and security

Fast does not have to mean fragile.

Every project is held to the same standard, whatever the service. It is the standard we build and run PMC to every day.

  • Fast to deliver

    Results in weeks, not quarters.

    • A working version at the end of every short cycle
    • Releases through an automated pipeline, not by hand
    • Small changes shipped often, so value arrives early
  • Built to last

    Software your team can still understand and change years from now.

    • Every change built and tested automatically before it is merged
    • Unit, API and end-to-end tests in a real browser
    • Documentation and a clean handover, or we run it for you
  • Secure from day one

    Security is part of the build, not a check at the end.

    • OWASP Top 10 and BSI IT-Grundschutz as the reference
    • Dependencies and images scanned for known vulnerabilities in every build
    • Access by role, changes logged, secrets kept out of the code
How we work

From manual click-throughs to tests on every change.

  1. Choose the journeys

    We start with the journeys that would hurt most if they broke, such as sign-in, ordering or approval.

  2. Write the tests

    End-to-end, API and load tests, written so your developers can extend them.

  3. Wire them into the pipeline

    The tests run on every change, the most important ones first.

  4. Report and extend

    Every run ends with a report and screenshots; new features bring new tests.

Afraid to change an application nobody has tested?

We record what it does today in automated tests first, so every later change can be checked against it.

Plan your safety net
Ways to work with us

Choose how much of the work you hand over.

From one clearly scoped project to a team inside your business and the long-term running of what we built. Every model has one accountable partner: Virtual Eye.

  • For a defined result

    Fixed-scope project

    You know what you get before the build starts: a concept, a prototype and a fixed scope come first.

    • A workshop on your process and the result you need
    • Concept, prototype and fixed scope before production code
    • A working version at the end of every short cycle
  • When the problem is not yet clear

    Forward deployed team

    A small Virtual Eye team works inside your business, learns how work and money really move, and delivers the solution with your people.

    • One lead for management, plus the engineers who build
    • Outcome and scope agreed in writing
    • A demo every week
  • For software you already run

    Takeover and modernisation

    We take over an existing application, make it safe to change, then develop it further step by step.

    • What exists is documented and tested first
    • Stabilised before anything new is added
    • Further development in small, tested releases
  • After go-live

    Run and evolve

    We host, monitor, update and support your applications on our servers, in your cloud or on-premises.

    • Monitoring and alerts that go straight to our team
    • Backups, updates and security patches
    • Support and further development from the team that built it
Customers

What customers say about working with us.

Quotes about the Virtual Eye team from PMC projects: the same people who would work on yours.

“Well thought-out concepts, tailored precisely to us. Very competent and always friendly, even during the stressful implementation phase.”
Iris HummelManager Infrastructure Services Sales DACH, Hewlett Packard EnterpriseTranslated from German
“PMC provides valuable support in day-to-day business and the team is very reliable, serious and friendly!”
Hao LiCentral Project Office PMO, Allianz Global Corporate & Specialty SE
“As a customer from day one, we have found reliable, fitting solutions with Virtual Eye throughout the years. Above all, the fast and flexible service.”
Sebastian StepferExecutive Director Public Safety EMEA Region, HexagonTranslated from German
Tech stack

The tools we use for this.

We choose them for your systems and your team, and we document every choice.

Manual, automated and performance testing, with a report for every run.

Manual and API testing

  • Postman
  • SoapUI
  • Swagger
  • Fiddler
  • Charles Proxy

Test management and reporting

  • Allure Report
  • ReportPortal
  • Cucumber
  • SpecFlow
  • Robot Framework

Test automation

  • Playwright
  • Selenium
  • Cypress
  • Appium
  • Detox
  • Puppeteer
  • WebdriverIO
  • Espresso
  • XCTest
  • Jest
  • Vitest
  • xUnit
  • JUnit
  • SonarQube

Performance testing

  • k6
  • Apache JMeter
  • Gatling
  • Grafana
Your technology is not listed?

Tell us what you run. If we have not worked with it yet, we say so, and tell you how we would approach it.

Talk to our engineersSee all technologies
Industries we serve

Test automation for the industries we know

Years of PMC have taught us how these industries approve, buy, report and get audited.

Banks

Tests that document what was checked, for every release an auditor may ask about.

  • Regression suites with reports
  • Role and permission tests
  • Test evidence kept per release
Questions

Questions teams ask before they start.

Which tests should we automate first?

The journeys that would hurt most if they broke: sign-in, your main business process and anything involving money. We start there and add to the suite with every release.

Can you test an application you did not build?

Yes. End-to-end tests work through the browser like a user, so they need no access to the source code.

Where do the tests run?

In your pipeline on every change, and on a schedule against staging or production, with a report after every run.

What about tests that fail at random?

They are fixed or removed, so a red run always means a real problem and the team keeps trusting the suite.

Do you use production data in tests?

No personal data is copied from production. Test data mirrors real cases, so the tests stay realistic.

Tell us what you want to build.

Describe the process, the systems involved and when it should go live. We reply with a first assessment and the next step.

Or write to us directly: hello@virtual-eye.com

What happens next?

  1. You write to us

    What you want to build, the systems involved and when it should go live.

  2. A first assessment

    We reply with a first assessment and the next step.

  3. A workshop

    On your process and the result you need, before any technology is chosen.

  4. A fixed scope

    A concept, a prototype and a fixed scope before the first line of production code.