Integration Testing – a thought experiment
summary
Claim: integration tests must move between components — start at the app and expect the COTS to call back — otherwise the test is a component test. Use published interface specs (payment codes like 00 success or 08 do not honor; Chromecast errors such as media unknown, aborted, source buffer failure) to generate scenarios. Replace fragile end-to-end setups by use stubs to inject errors that send those exact messages and verify the system’s responses, which is faster and repeatable.
AI-written summary · about
chapters (4)
related talks
44mTesting: Integration Tests - The good, bad and ugly
58mIntegration Testing from the Trenches
01h 20mIntegration Testing from the Trenches
40mIntegration Testing from the Trenches - Rebooted
42mIntegration Tests Are Bogus
45mTesting in a Service-Based Environment, Staged Acceptance
22mContract Testing – An efficient way for integration testing
02h 58mOverview of Testing in Our Applications