TopicsTesting
Testing
Pyramid, contracts, property-based tests, doubles, and flakes you can defend in interviews.
Common tags: test-pyramid, contracts, property-based, flakes
- Testing
Load, Chaos & Production Validation — Shadow Traffic, Canaries & Game Days
Cluster · Testing Strategies
Load checks capacity and latency. Chaos checks graceful failure. Shadow traffic, canaries, synthetics, and game days sit above the pyramid, always with an SLO abort and a blast-radius limit.
Open study →- testing
- load
- chaos
- canary
- game-day
- interview
- Testing
Testing Strategies — Pyramid, Contracts, Property-Based & Flakes
Cluster · Testing Strategies
Choose the cheapest test that would have caught the bug. Pyramid/Trophy allocate effort; contracts protect boundaries; property/fuzz find edge cases mocks miss; doubles need discipline; flakes destroy trust.
Open study →- testing
- test-pyramid
- testing-trophy
- contract-testing
- pact
- property-based-testing
- fuzzing
- test-doubles
- mocks
- flaky-tests
- interview
- Testing
Test Pyramid & Testing Trophy — Unit vs Integration vs E2E
Cluster · Testing Strategies
Unit = fast/narrow; integration = real collaborators; E2E = journeys but slow/flaky. Trophy shifts effort toward integration. Avoid ice-cream cone (mostly E2E).
Open study →- testing
- test-pyramid
- testing-trophy
- unit-tests
- integration-tests
- e2e
- interview
- Testing
Test Doubles — Mocks, Stubs, Fakes, Spies & When Not to Mock
Cluster · Testing Strategies
Mock/stub/fake/spy/dummy (Meszaros). Over-mocking couples tests to implementation; prefer fakes/testcontainers for domain logic.
Open study →- testing
- test-doubles
- mocks
- stubs
- fakes
- spies
- interview
- Testing
Property-Based & Fuzz Testing — Generators, Shrinking & Invariants
Cluster · Testing Strategies
Generators + invariants + shrinking find edge cases example tests miss. Hypothesis (Python) and fast-check (TS); fuzz parsers/protocols.
Open study →- testing
- property-based-testing
- fuzzing
- hypothesis
- fast-check
- interview
- Testing
Flaky Tests — Isolation, Time, Concurrency & Quarantine
Cluster · Testing Strategies
Root causes: time, randomness, shared state, async races, order dependence, externals. Quarantine vs fix; retries hide bugs; freeze clocks and isolate state.
Open study →- testing
- flaky-tests
- test-isolation
- quarantine
- determinism
- interview
- Testing
Contract Testing — Consumer-Driven Contracts vs Schema Contracts
Cluster · Testing Strategies
Consumer-driven (Pact) vs provider schema (OpenAPI/AsyncAPI/Protobuf) vs shared-env e2e. Contracts catch breaking API changes in CI without staging.
Open study →- testing
- contract-testing
- pact
- openapi
- schema-contracts
- interview