thevar1able/ClickHouse
1
0
Fork 0
mirror of https://github.com/ClickHouse/ClickHouse.git synced 2024-11-15 20:24:07 +00:00
Code Issues Packages Projects Releases Wiki Activity
2347c9339c
ClickHouse/tests/integration/test_tcp_handler_http_responses/test_case.py

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

40 lines
1.0 KiB
Python
Raw Normal View History

test that the tcp handler returns correct http responses I have added two tests. One checks the usual scenario where the instance's config specifies a `http_port`. In that case, we expect the `http_port` to be part of the response. The other scenario checks what happens when the config doesn't specify a `http_port`. It's hard to nail down the expectation there without hardcoding the error response (which is not what we generally want) but I'm mainly checking that no HTTP port is mentioned. This particular test would have failed before my previous fix, because the TCP handler wouldn't have managed to send back an HTTP response and `requests.post` would have thrown an exception.
2021-08-07 10:54:54 +00:00
"""Test HTTP responses given by the TCP Handler."""
from pathlib import Path
import pytest
from helpers.cluster import ClickHouseCluster
import requests
cluster = ClickHouseCluster(__file__)
node_with_http = cluster.add_instance(
Apply black formatter to all *.py files in the repo
2022-03-22 16:39:58 +00:00
"node_with_http", main_configs=["configs/config.d/http-port-31337.xml"]
test that the tcp handler returns correct http responses I have added two tests. One checks the usual scenario where the instance's config specifies a `http_port`. In that case, we expect the `http_port` to be part of the response. The other scenario checks what happens when the config doesn't specify a `http_port`. It's hard to nail down the expectation there without hardcoding the error response (which is not what we generally want) but I'm mainly checking that no HTTP port is mentioned. This particular test would have failed before my previous fix, because the TCP handler wouldn't have managed to send back an HTTP response and `requests.post` would have thrown an exception.
2021-08-07 10:54:54 +00:00
)
HTTP_PORT = 31337
node_without_http = cluster.add_instance(
Apply black formatter to all *.py files in the repo
2022-03-22 16:39:58 +00:00
"node_without_http", main_configs=["configs/config.d/no-http-port.xml"]
test that the tcp handler returns correct http responses I have added two tests. One checks the usual scenario where the instance's config specifies a `http_port`. In that case, we expect the `http_port` to be part of the response. The other scenario checks what happens when the config doesn't specify a `http_port`. It's hard to nail down the expectation there without hardcoding the error response (which is not what we generally want) but I'm mainly checking that no HTTP port is mentioned. This particular test would have failed before my previous fix, because the TCP handler wouldn't have managed to send back an HTTP response and `requests.post` would have thrown an exception.
2021-08-07 10:54:54 +00:00
)
Apply black formatter to all *.py files in the repo
2022-03-22 16:39:58 +00:00
test that the tcp handler returns correct http responses I have added two tests. One checks the usual scenario where the instance's config specifies a `http_port`. In that case, we expect the `http_port` to be part of the response. The other scenario checks what happens when the config doesn't specify a `http_port`. It's hard to nail down the expectation there without hardcoding the error response (which is not what we generally want) but I'm mainly checking that no HTTP port is mentioned. This particular test would have failed before my previous fix, because the TCP handler wouldn't have managed to send back an HTTP response and `requests.post` would have thrown an exception.
2021-08-07 10:54:54 +00:00
@pytest.fixture(scope="module")
def start_cluster():
try:
cluster.start()
yield cluster
finally:
cluster.shutdown()
Apply black formatter to all *.py files in the repo
2022-03-22 16:39:58 +00:00
test that the tcp handler returns correct http responses I have added two tests. One checks the usual scenario where the instance's config specifies a `http_port`. In that case, we expect the `http_port` to be part of the response. The other scenario checks what happens when the config doesn't specify a `http_port`. It's hard to nail down the expectation there without hardcoding the error response (which is not what we generally want) but I'm mainly checking that no HTTP port is mentioned. This particular test would have failed before my previous fix, because the TCP handler wouldn't have managed to send back an HTTP response and `requests.post` would have thrown an exception.
2021-08-07 10:54:54 +00:00
def test_request_to_http_full_instance(start_cluster):
Apply black formatter to all *.py files in the repo
2022-03-22 16:39:58 +00:00
response = requests.get(f"http://{node_with_http.ip_address}:9000")
test that the tcp handler returns correct http responses I have added two tests. One checks the usual scenario where the instance's config specifies a `http_port`. In that case, we expect the `http_port` to be part of the response. The other scenario checks what happens when the config doesn't specify a `http_port`. It's hard to nail down the expectation there without hardcoding the error response (which is not what we generally want) but I'm mainly checking that no HTTP port is mentioned. This particular test would have failed before my previous fix, because the TCP handler wouldn't have managed to send back an HTTP response and `requests.post` would have thrown an exception.
2021-08-07 10:54:54 +00:00
assert response.status_code == 400
assert str(HTTP_PORT) in response.text
Apply black formatter to all *.py files in the repo
2022-03-22 16:39:58 +00:00
test that the tcp handler returns correct http responses I have added two tests. One checks the usual scenario where the instance's config specifies a `http_port`. In that case, we expect the `http_port` to be part of the response. The other scenario checks what happens when the config doesn't specify a `http_port`. It's hard to nail down the expectation there without hardcoding the error response (which is not what we generally want) but I'm mainly checking that no HTTP port is mentioned. This particular test would have failed before my previous fix, because the TCP handler wouldn't have managed to send back an HTTP response and `requests.post` would have thrown an exception.
2021-08-07 10:54:54 +00:00
def test_request_to_http_less_instance(start_cluster):
Apply black formatter to all *.py files in the repo
2022-03-22 16:39:58 +00:00
response = requests.post(f"http://{node_without_http.ip_address}:9000")
test that the tcp handler returns correct http responses I have added two tests. One checks the usual scenario where the instance's config specifies a `http_port`. In that case, we expect the `http_port` to be part of the response. The other scenario checks what happens when the config doesn't specify a `http_port`. It's hard to nail down the expectation there without hardcoding the error response (which is not what we generally want) but I'm mainly checking that no HTTP port is mentioned. This particular test would have failed before my previous fix, because the TCP handler wouldn't have managed to send back an HTTP response and `requests.post` would have thrown an exception.
2021-08-07 10:54:54 +00:00
assert response.status_code == 400
assert str(HTTP_PORT) not in response.text
Apply black formatter to all *.py files in the repo
2022-03-22 16:39:58 +00:00
assert "8123" not in response.text
Reference in New Issue Copy Permalink