mirror of
https://github.com/zulip/zulip.git
synced 2025-11-04 05:53:43 +00:00
243d8ffc51
This new test runs each generated curl example against the Zulip API, checking whether it returns successfully without errors. Significantly modified by tabbott for simplicity.
85 lines
3.3 KiB
Python
85 lines
3.3 KiB
Python
import glob
|
|
import json
|
|
import shlex
|
|
import subprocess
|
|
import markdown
|
|
|
|
from zulip import Client
|
|
from zerver.lib.bugdown import api_code_examples
|
|
from zerver.models import get_realm
|
|
|
|
# whitelisted_files is a list of endpoints which have been
|
|
# migrated to the example generation system and can thus be
|
|
# tested.
|
|
whitelisted_files = [
|
|
"get-messages.md",
|
|
]
|
|
|
|
def test_generated_curl_examples_for_success(client: Client) -> None:
|
|
authentication_line = "{}:{}".format(client.email, client.api_key)
|
|
# A limited markdown engine that just processes the code example syntax.
|
|
realm = get_realm("zulip")
|
|
md_engine = markdown.Markdown(extensions=[api_code_examples.makeExtension(
|
|
api_url=realm.uri + "/api")])
|
|
|
|
for file_name in glob.glob("templates/zerver/api/*.md"):
|
|
documentation_lines = open(file_name, "r").readlines()
|
|
for line in documentation_lines:
|
|
# A typical example from the markdown source looks like this:
|
|
# {generate_code_example(curl, ...}
|
|
if not line.startswith("{generate_code_example(curl"):
|
|
continue
|
|
|
|
# To do an end-to-end test on the documentation examples
|
|
# that will be actually shown to users, we use the
|
|
# markdown rendering pipeline to compute the user-facing
|
|
# example, and then run that to test it.
|
|
curl_command_html = md_engine.convert(line.strip())
|
|
curl_command_text = curl_command_html[len("<p><code>curl\n"):-len("</code></p>")]
|
|
|
|
curl_command_text = curl_command_text.replace(
|
|
"BOT_EMAIL_ADDRESS:BOT_API_KEY", authentication_line)
|
|
|
|
print("Testing %s ..." % (curl_command_text.split("\n")[0],))
|
|
|
|
# Turn the text into an arguments list.
|
|
generated_curl_command = [
|
|
x for x in shlex.split(curl_command_text) if x != "\n"]
|
|
|
|
response = None
|
|
try:
|
|
# We split this across two lines so if curl fails and
|
|
# returns non-JSON output, we'll still print it.
|
|
response = subprocess.check_output(generated_curl_command).decode('utf-8')
|
|
response = json.loads(response)
|
|
assert(response["result"] == "success")
|
|
except (AssertionError, Exception):
|
|
error_template = """
|
|
Error verifying the success of the API documentation curl example.
|
|
|
|
File: {file_name}
|
|
Line: {line}
|
|
Curl Command:
|
|
{curl_command}
|
|
Response:
|
|
{response}
|
|
|
|
This test is designed to check each generate_code_example(curl) instance in the
|
|
API documentation for success. If this fails then it means that the curl example
|
|
that was generated was faulty and when tried, it resulted in an unsuccessful
|
|
response.
|
|
|
|
Common reasons for why this could occur:
|
|
1. One or more example values in zerver/openapi/zulip.yaml for this endpoint
|
|
do not line up with the values in the test database.
|
|
2. One or more mandatory parameters were included in the "exclude" list.
|
|
|
|
To learn more about the test itself, see zerver/openapi/test_curl_examples.py.
|
|
"""
|
|
print(error_template.format(
|
|
file_name=file_name,
|
|
line=line,
|
|
curl_command=generated_curl_command,
|
|
response=json.dumps(response, indent=4)))
|
|
raise
|