// Verify the control channel socket no longer exists.
EXPECT_FALSE(fileExists(socket_path_));
- // With no command channel, should still receive the response. The config contains random
- // socket name (/tmp/kea-<value-changing-each-time>/kea4.sock), so the
- // hash will be different each time. As such, we can do simplified checks:
+ // With no command channel, should still receive the response.
+ // The config contains random socket name
+ // (/tmp/kea-<value-changing-each-time>/kea4.sock), so the hash will
+ // be different each time. As such, we can do simplified checks:
// - verify the "result": 0 is there
// - verify the "text": "Configuration successful." is there
EXPECT_NE(response.find("\"result\": 0"), std::string::npos);
int status;
ConstElementPtr args = parseAnswer(status, rsp);
EXPECT_EQ(CONTROL_RESULT_SUCCESS, status);
- // the parseAnswer is trying to be smart with ignoring hash.
+ // The parseAnswer is trying to be smart with ignoring hash.
// But this time we really want to see the hash, so we'll retrieve
// the arguments manually.
args = rsp->get(CONTROL_ARGUMENTS);
/// @param response_str a string containing the whole HTTP
/// response received.
///
- /// @return An HttpResponse constructed from parsing the response string.
+ /// @return An HttpResponse constructed by parsing the response string.
HttpResponsePtr parseResponse(const std::string response_str) {
HttpResponsePtr hr(new HttpResponse());
HttpResponseParser parser(*hr);
ASSERT_TRUE(client);
// Send the command. This will trigger server's handler which receives
- // data over the HTTP socket. The server will start sending
- // response to the client.
+ // data over the HTTP socket. The server will start sending response
+ // to the client.
ASSERT_NO_THROW(client->startRequest(buildPostStr(command)));
runIOService();
ASSERT_TRUE(client->receiveDone());
EXPECT_FALSE(fileExists(socket_path_));
// With no command channel, should still receive the response.
- // The config contains random socket name socket name
+ // The config contains random socket name
// (/tmp/kea-<value-changing-each-time>/kea6.sock), so the hash will
// be different each time. As such, we can do simplified checks:
// - verify the "result": 0 is there