How do I check reliability?
Understand the concept
Reliability means the operation behaves predictably when dependencies fail, time out or return uncertain outcomes. It includes recovery after a crash, bounded resource use and preservation of business state. A happy-path test cannot prove that retries, rollback and cleanup are correct.
Important ideas
-
Follow timeout, retry, crash and partial-failure paths.
-
Check transaction boundaries, cleanup and duplicate processing.
-
An external action may succeed even if its response is lost.
-
Trace what is durable before and after each external effect, and check whether a retry can repeat that effect.
Can you explain it without the notes?
How do I check reliability?
Use your own words. Explain an example and one limitation before checking the explanation.
Check your explanation
Reliability means the operation behaves predictably when dependencies fail, time out or return uncertain outcomes. It includes recovery after a crash, bounded resource use and preservation of business state. A happy-path test cannot prove that retries, rollback and cleanup are correct.
Turn this concept into a clear answer.
- Identify a specific failure window and the state a later retry or operator will observe.
Adapted from 11_AI_CODE_REVIEW.md · “How do I check reliability?”. Examples are study fragments; framework behavior can depend on your version.