error-handling-completeness

Error-handling completeness covers timeouts, retries, and exception management for external API calls. Verify try-catch blocks wrap all API requests, add retry logic with backoff patterns, log failures, and display user-facing error messages to prevent silent crashes and improve resilience.

Database access and file I/O require explicit error handling for connection failures, read/write timeouts, and missing resources. Implement try-catch coverage, add logging for each failure mode, provide meaningful user messages, and consider retry strategies for transient errors to maintain application stability.

Asynchronous operations and JSON parsing need dedicated error handlers to catch parsing exceptions and promise rejections. Log each error with context, implement timeouts on async calls, provide clear user feedback when data is invalid, and add retry logic for network-dependent operations.

Logging captures what went wrong for debugging; user-facing messages prevent confusion and improve experience. Error-handling completeness ensures both exist: logs contain technical details and stack traces, while users receive actionable, non-technical messages so they understand what happened and what to do next.

Yes, error-handling completeness identifies high-risk paths in external calls, database access, and user-facing code. It verifies try-catch coverage, validates retry and backoff patterns, ensures logging exists, and provides remediation guidance to prevent production crashes and improve code resilience.

Timeouts prevent indefinite waiting by stopping requests after a set duration; retries attempt recovery after failure with backoff delays. Error-handling completeness ensures both: timeouts prevent hangs, retries with exponential backoff handle transient failures, and logging tracks all attempts for observability.