Testing Feature Interactions in Payments
summary
Property‑based testing with Quviq QuickCheck generates hundreds of API sequences against a local Kivra‑in‑a‑box Docker replica of the payments stack to exercise mandate‑based automatic payments for Kivra (6.2M users). A Trustly mock lets tests inject delays, dropped notifications and state flips; tests uncover an unexpected active→failed transition, cases where an invoice is auto‑paid without an approved notify, and dozens of small negative‑case bugs found and fixed. The three‑month pilot produces reproducible shrunk counterexamples and new regression tests.
AI-written summary · about
chapters (10)
- 0:00Testing feature interactions
- 3:12Kirara payment system
- 6:24Testing goals and methodology
- 10:38Modeling mandates and state machines
- 13:50Mocks for external services
- 16:46Fault injections and edge cases
- 19:11Feature interactions in payments
- 22:47Manual testing limitations
- 23:31Project findings and conclusions
- 24:37Q&A on OpenAPI limits
related talks
45mTesting Web Services with QuickCheck
08mVariations During Testing
35mTest automation guide: How to move away from chain tests
44mAPI Testing following the Test Pyramid
43mAutomated Tests Are Not Enough
21mProperty-based testing - let your testing library work for you
01h 05mMicrotesting
46mQA to QE: Scaling Quality with Ownership, Code, and Culture