Integration tests

Automated checks of two or more components together, often with a real database or queue.

Mandatory for 23 of 46 product types. Usually run by a developer.

What it catches

• wrong wiring
• schema drift
• transaction faults

What it misses

• user-visible flows
• third-party outages

Which product types need it and why

Done conditions used on playbook pages

Each mandatory cell has its own done condition, written for that product type.

• accounting and invoicing SaaS (Fintech): A transaction posted in the sandbox bank appears once in the bank feed with the same date, amount and payee.
• buy now pay later service (Fintech): A refund, a partial capture and a cancelled order sent through the merchant API each change the shopper's plan in the app to the matching amount.
• clinical trial management software (Healthcare): Lab, eCOA and device files imported into the EDC land on the right subject and visit, with the same values and units as the source file.
• data pipeline (Infrastructure and developer products): An end-to-end run against staging copies of each source and target loads a file above the largest size seen in production with no rows lost, and when the source stream stops sending mid-run, the run is reported as stalled instead of complete.
• ecommerce store (Commerce): Order, payment and fulfilment status match across the storefront, payment provider and warehouse system for paid, shipped, cancelled and refunded orders.
• electronic health record system (Healthcare): Every order type placed in a test chart reaches its target lab, pharmacy or specialty worklist, and an order with no valid target is refused at entry with a message.
• email marketing platform (B2B SaaS): Clicking one-click unsubscribe in a Gmail or Yahoo seed inbox removes the contact once, and a link scanner opening the same link leaves the contact shown as subscribed in the audience list.
• ERP system (B2B SaaS): Every field sent by each feeder system arrives in the ledger posting, and a missing required field rejects the batch with a visible error.
• EV charging app (Infrastructure and developer products): Start, stop and meter messages between the backend and a test charger, and through a roaming partner, produce the same session record on both sides.
• expense management tool (Fintech): A card transaction from the issuer processor appears once on the cardholder's expense list with the same amount, currency and merchant, and a reversal removes it.
• identity and access management service (B2B SaaS): With a directory connector enabled and MFA off for a test app, a sign-in with the right username and a wrong password is refused straight after that user's successful sign-in.
• insurance app (Fintech): An insurance score or vehicle record returned by the data vendor lands in the policy record with the same value and tier the vendor sent.
• lending platform (Fintech): A repayment posted by the processor updates the loan balance and next due date on the servicing screen, and a returned payment reverses both.
• loyalty program app (Commerce): After points move to a new ledger or a second program merges in, the balance and tier a member sees in the app, at the point of sale and in a partner channel equal the converted balance in the new ledger, and a new purchase in each channel credits points once.
• messaging app (Consumer apps): With the cloud network gateway in front of the chat backend switched off in staging and then restored, phones reconnect without the app freezing, every message sent during the outage arrives once and each recipient gets one notification.
• mobile banking app (Fintech): A test debit card authorisation and its later settlement create one ledger entry, and no overdraft fee appears when the balance covered the amount at authorisation.
• neobank (Fintech): A card payment, a refund and an incoming transfer made in the sandbox each appear once in both the app ledger and the partner bank feed.
• patient portal (Healthcare): Every message type sent from the portal appears in the EHR inbox for the right care team and is filed to the patient's chart.
• software as a medical device (Healthcare): Each command the app sends reaches the test device once, the device confirms it, and the app shows the confirmed value rather than the requested one.
• SDK or client library (Infrastructure and developer products): A proxy capture of a sample host app shows the SDK sends only the data types in its privacy manifest, and nothing before the host app's consent call.
• subscription box service (Commerce): Subscription status, next billing date and next shipment date match across the storefront, billing provider and fulfilment system after a skip, pause and cancel.
• travel booking app (Commerce): A cancellation or schedule change sent by each connected supplier appears on the traveller's booking and opens a refund case.
• video conferencing tool (B2B SaaS): A proxy capture of app open shows no third-party SDK sending device data before the user picks that SDK's feature.

Tools

Alphabetical. Not recommendations.