Mocking HTTP Calls in Unit Tests

Unit testing is an important part of building reliable software in any language, including C++. But testing code that makes HTTP requests can be tricky - we don't want our tests to actually send network traffic or rely on a particular server being available.

The solution is to use mocking or faking to replace the real HTTP calls with simulated versions that always return a pre-configured response.

There are a number of C++ mocking libraries available that support this, such as GoogleMock or FakeIt. But even without a mocking library, we can apply the basic principle.

Here's an example of how we might structure our code to allow mocking of cpr::Get calls in unit tests:

1#include <cpr/cpr.h>
2#include <functional>
3#include <iostream>
4
5using HttpGetFunc = std::function<cpr::Response(
6  cpr::Url, cpr::Parameters)>;
7
8int getNumberOfThings(HttpGetFunc getter) {
9  cpr::Url url{"http://www.example.com/things"};
10  cpr::Parameters params{{"type", "widgets"}};
11
12  cpr::Response r = getter(url, params);
13
14  if (r.status_code == 200) {
15    return std::stoi(r.text);
16  } else {
17    return -1;
18  }
19}
20
21cpr::Response cprGet(cpr::Url url,
22  cpr::Parameters params) {
23  return cpr::Get(url, params);
24}
25
26int main() {
27  int num = getNumberOfThings(cprGet);
28  std::cout << "There are " << num
29    << " things.\n";
30}

Here the actual business logic is in the getNumberOfThings function. But instead of calling cpr::Get directly, it accepts a getter parameter, which is a function matching the signature of cpr::Get.

In the "production" code path, we call getNumberOfThings(cpr::Get), passing the real cpr::Get function.

But in unit tests, we can pass a mock or fake function that returns a predefined response without making any network calls:

1#include <gtest/gtest.h>
2
3cpr::Response mockGet(cpr::Url url, cpr::Parameters params) {
4  cpr::Response fakeResponse;
5  fakeResponse.status_code = 200;
6  fakeResponse.text = "42";
7  return fakeResponse;
8}
9
10TEST(ThingsTest, GetNumberOfThings) {
11  int num = getNumberOfThings(mockGet);
12  ASSERT_EQ(num, 42);
13}

Our mockGet function always returns a 200 OK response with the text "42", regardless of the URL or parameters passed to it. This allows us to test that getNumberOfThings parses the response correctly without needing any real network access.

Of course, this is a simplified example. In a real application, we'd probably want to check that getNumberOfThings constructs the expected URL and parameters. And we'd want to test error cases by having the mock function return different status codes.

But the principle is the same - by abstracting the HTTP call behind a function interface, we can easily substitute mocks or fakes in tests to avoid relying on network access and make our tests faster and more reliable.