End-to-End Integration Testing: Pay in Instalments

Smoke testing, new feature testing, retesting, system end-to-end testing, and regression testing on connecting a real external instalment payment service.

Your first day on the team

Krista, Product Manager (PM)

Hi! What’s your name?

Application under test
Order paymentOrder #1024

Amount due: €49.90

Payment method

Quick reference

Smoke testing

A short check of the most important functions of a new build: does the application open, do the key elements work. If the smoke test fails, the build goes back to the developer — further testing makes no sense.

Retesting

Checking a specific defect again after it has been fixed: you repeat the steps that reproduced it and make sure the defect is gone.

New feature testing

Checking that a new feature works according to the requirements: the main scenario, alternative scenarios, and error handling.

Regression testing

Checking that the changes have not broken what already worked. It helps to define the regression set in advance — before work on the new feature starts.

System end-to-end (E2E) testing

Checking the user’s whole journey through all connected systems: the interface, our server, external services (for example, a payment service), and back to the result the user sees. Such checks find defects at the joints between systems that are invisible when each part is tested on its own.

Mocks and test environments

A mock stands in for an external service and answers the way the developer intended, so it accepts wrong data too. An external service’s test environment is the real service with test data: it checks requests for real, but no real money is charged. E2E needs exactly that.

Business outcome or technical failure

Klarna declining instalments is an expected business outcome described in the requirements. An integration error is a technical failure: the request was not processed. On a decline the customer sees “Payment failed”; on an integration error there is no decision from Klarna at all.