Files
zulip/tools/test-api
Greg Price a099e698e2 py3: Switch almost all shebang lines to use python3.
This causes `upgrade-zulip-from-git`, as well as a no-option run of
`tools/build-release-tarball`, to produce a Zulip install running
Python 3, rather than Python 2.  In particular this means that the
virtualenv we create, in which all application code runs, is Python 3.

One shebang line, on `zulip-ec2-configure-interfaces`, explicitly
keeps Python 2, and at least one external ops script, `wal-e`, also
still runs on Python 2.  See discussion on the respective previous
commits that made those explicit.  There may also be some other
third-party scripts we use, outside of this source tree and running
outside our virtualenv, that still run on Python 2.
2017-08-16 17:54:43 -07:00

41 lines
943 B
Python
Executable File

#!/usr/bin/env python3
from __future__ import print_function
from __future__ import absolute_import
import os
import sys
# check for the venv
from lib import sanity_check
sanity_check.check_venv(__file__)
import django
TOOLS_DIR = os.path.dirname(__file__)
ROOT_DIR = os.path.dirname(TOOLS_DIR)
sys.path.insert(0, ROOT_DIR)
from zulip import Client
from tools.lib.test_server import test_server_running
from tools.lib.api_tests import test_the_api
os.environ['DJANGO_SETTINGS_MODULE'] = 'zproject.test_settings'
django.setup()
from zerver.models import get_user, get_realm
with test_server_running():
email = 'iago@zulip.com' # Iago is an admin
realm = get_realm("zulip")
api_key = get_user(email, realm).api_key
site = 'http://127.0.0.1:9981'
client = Client(
email=email,
api_key=api_key,
site=site)
print("Running API tests...")
test_the_api(client)
print("API tests passed!")