A parking-fine fee calculator changed overnight. Which test layer best gives fast feedback on that logic alone?
Select an answer to reveal the explanation.
Short Explanation
Unit tests are the desk calculator on the counter—same math, fake neighbors. They stay in one process so the fee change is checked in seconds, not after spinning up a cluster.
Full Explanation
Unit tests target one service’s logic with in-process doubles. They do not call a real OCI Queue, invoke a live Function, or require an OKE cluster. That speed is the point for pure logic changes. Real collaborators belong in integration or thin end-to-end layers when I/O behavior itself is under test.