Service
Test automation & QA
Regressions caught before production.
Automated tests that run on every change to your code. This is the daily work of a QA engineer on mass payment systems.
End-to-end
Critical journeys
Integration
APIs, database, services
Unit
Logic, rules, calculations
Tools: Unit tests, integration tests, end-to-end tests, API tests, regression tests, and continuous integration.
What's covered
A What to test, at which level, in which order., On the critical code first., On the journeys that must not break. and a That runs everything on every pull request. to run them all.
Hover or tap the underlined terms for details.
What you receive
- Deliverable
Test plan
Journeys and rules to cover, prioritized by risk.
- Deliverable
Automated test suite
In your repository, maintainable by your team.
- Deliverable
CI pipeline
Tests run on every pull request and block the merge when they fail.
- Deliverable
Coverage report
What is covered, and what is not yet.
How it unfolds
Review
Where past bugs came from.
Prioritization
Riskiest code first.
Test writing
Starting with the bugs you already had.
CI and handover
Tests made unavoidable, team trained.
See also
- See details
Service
Web & app development
Websites and web applications that load fast, stay maintainable and run on infrastructure you control.
- See details
Domain expertise
European payments
Knowledge of SEPA transfers, instant payments, direct debits and ISO 20022 messages, from quality assurance on payment systems.