What tests would you include for geocoding integration?

What tests would you include for geocoding integration?

• A. Test only the local validation logic without invoking the external geocoding service.
• B. Mock geocoding responses, test success/failure, retry logic, rate limit handling, and storage of coordinates.
• C. Rely on manual testing by geographers interpreting address maps.
• D. Use unit tests that only check formatting of input addresses.

Answer: (B)

Testing geocoding integration centers on how your application communicates with the external geocoding service and how it handles the service’s responses. The best approach is to mock geocoding responses and verify end-to-end behavior: success paths where coordinates are returned and stored, and failure paths where the service is unavailable, returns invalid data, or times out. Include tests for retry logic and backoff, rate-limiting handling, and ensuring that the resulting latitude/longitude are persisted correctly for downstream use. This approach keeps tests fast, deterministic, and capable of catching issues in the integration layer, data handling, and error management.

Why the other options aren’t as strong: testing only local validation ignores the actual interaction with the external service and the data returned by it; manual testing by geographers is valuable but is not a scalable automated testing strategy for CI; and unit tests that only check input formatting fail to exercise the external call and the storage of coordinates, which are essential parts of the integration.