Konrad Kowalski (rootsher)Principal Platform & Reliability Architect101010010111110011001111011101111001101010110000

Regression Testing

posts (6)

  1. Testing Through Layers: From Code to Infrastructure7/9

    Migration Tests and Data Tests: Safe State Changes

    A migration test checks schema and data changes, while a data test protects state compatibility. This layer decides whether a release can be rolled back safely.

  2. Testing Through Layers: From Code to Infrastructure6/9

    Regression Tests and Smoke Tests: The Gate Before Release

    A regression test closes a bug that already passed once, while a smoke test checks whether a version is even worth testing further.

  3. Testing Through Layers: From Code to Infrastructure5/9

    E2E Tests and Visual Regression Tests: The Full User Path

    An E2E test walks through the system the way a user does, while a visual regression test protects appearance. They are powerful but expensive, so they should…

  4. Testing Through Layers: From Code to Infrastructure2/9

    Component Tests and Snapshot Tests: A Small Application Fragment

    A component test checks a small part of the application as behavior, while a snapshot test records its output. Both sit close to the code, but they answer…

  5. Testing Through Layers: From Code to Infrastructure1/9

    Unit Tests: Fast Diagnosis Near the Code

    A unit test checks the smallest useful unit of behavior without starting the whole system. Its value is speed and precise diagnosis.

  6. series · 9 parts

    Testing Through Layers: From Code to Infrastructure

    This series organizes test types by the place where they catch risk cheapest: from a small code decision to the production environment.