Not everything should be automated.

The problem

Why customers call us.

Automation checks what you already thought of. It does not notice that the new screen is unusable, that the migrated data is subtly wrong, or that the cutover plan has a gap at hour eleven.

What we take responsibility for

Our scope.

• Exploratory and risk-based manual testing
• UAT preparation, support and coordination with business users
• Accessibility testing against WCAG 2.2 and the European Accessibility Act
• Data integrity and migration testing
• Cutover and go-live rehearsal testing
• Performance and load testing on the same processes as your functional coverage

What you get

Deliverables.

• Test charters and session reports
• UAT plan and support
• Accessibility audit with prioritised findings
• Data validation results
• Cutover test protocol
• Performance test report with bottleneck analysis

Platforms and tools

What we work with.

• NeoLoad
• K6
• JMeter
• Gatling
• Axe · WAVE · screen readers
• SQL and data comparison tooling
• Tricentis qTest

How we start

Three steps.

1. 01

   We agree the risk areas — where would a defect actually hurt

2. 02

   Charters, scope and acceptance criteria

3. 03

   Execution with findings you can act on, not a spreadsheet of observations

From our work

An example.

For a German defence and industrial group we build performance and load tests around the same critical SAP processes that are covered functionally — one process model, two kinds of evidence.

Questions we get asked

Straight answers.