A code-enforcement worker must prove it can publish, consume, and delete on OCI Queue the way production will—including visibility timeout behavior. Which test approach fits?
Select an answer to reveal the explanation.
Short Explanation
Visibility timeout is a real-clock behavior. An in-memory toy that never hides a message will not catch it. Integration tests use a real Queue or a faithful protocol stand-in.
Full Explanation
Integration tests prove the service can talk to collaborators the way production will—backing stores, Queue, or Functions. Mocking away I/O at this layer hides failures such as visibility-timeout handling. Unit-level doubles remain appropriate for pure logic, but Queue timing and protocol quirks need a real or faithful collaborator.