146 lines
5.7 KiB
Python
Raw Normal View History

#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.
"""Generate HTTP tests from YAML files
Each HTTP request is its own TestCase and can be requested to be run in
2015-04-08 00:00:03 +01:00
isolation from other tests. If it is a member of a sequence of requests,
prior requests will be run.
A sequence is represented by an ordered list in a single YAML file.
Each sequence becomes a TestSuite.
An entire directory of YAML files is a TestSuite of TestSuites.
"""
import glob
import inspect
import os
import unittest
from unittest import suite
import uuid
from gabbi import case
from gabbi import handlers
from gabbi import reporter
Extract suitemaking out of driver This creates a new module, suitemaker.py, which contains the code used to create a suite.GabbiSuite, which contains case.HTTPTestCase tests. This limits driver.py to being mostly code that is necessary to assemble the necessary information to create tests that are runnable by python test harnesses. This is distinguished from runner.py which assembles the necessary information to both create and _run_ tests itself. The idea here is that if the interface presented by test_suite_from_dict (both signature and that it returns a GabbiSuite) is preserved, then anything in suitemaker.py is welcome to change. The signature on test_suite_from_dict is the definition of what a caller (driver or runner or whatever else) needs to have learned: loader: the unittest.TestLoader which we might be able to default out of existence test_base_name: names help with test grouping so useful suite_dict: the main piece of the pie, the dict test_directory: the place where `data` can load files from host: the host any unqualified test goes to port: the port any unqualified test goes to fixture_module: the sole module from which fixtures come intercept: the wsgi app to intercept if any prefix: the url prefix host and intercept are mutually exclusive One can image it might be possible to replace host, port, prefix with a URL instead. If that were done than host and url would be mutually exclusive. If the signature of test_suite_from_dict changes then stuff in both driver and runner, in how they assemble the required info, would need to change. Note: For reasons unclear these changes have exposed some state management issues in test_runner, noted in a NOTE.
2016-06-03 15:07:57 +01:00
from gabbi import suitemaker
from gabbi import utils
2014-12-15 13:33:00 +00:00
def build_tests(path, loader, host=None, port=8001, intercept=None,
test_loader_name=None, fixture_module=None,
response_handlers=None, prefix='', require_ssl=False,
url=None):
"""Read YAML files from a directory to create tests.
Each YAML file represents an ordered sequence of HTTP requests.
:param path: The directory where yaml files are located.
:param loader: The TestLoader.
2015-06-17 12:16:24 +01:00
:param host: The host to test against. Do not use with ``intercept``.
:param port: The port to test against. Used with ``host``.
:param intercept: WSGI app factory for wsgi-intercept.
:param test_loader_name: Base name for test classes. Rarely used.
:param fixture_module: Python module containing fixture classes.
:param response_handers: ResponseHandler classes.
:type response_handlers: List of ResponseHandler classes.
:param prefix: A URL prefix for all URLs that are not fully qualified.
:param url: A full URL to test against. Replaces host, port and prefix.
:param require_ssl: If ``True``, make all tests default to using SSL.
2015-06-17 12:16:24 +01:00
:rtype: TestSuite containing multiple TestSuites (one for each YAML file).
"""
# Exit immediately if we have no host to access, either via a real host
# or an intercept.
if not bool(host) ^ bool(intercept):
raise AssertionError('must specify exactly one of host or intercept')
# If url is being used, reset host, port and prefix.
if url:
host, port, prefix, force_ssl = utils.host_info_from_target(url)
if force_ssl and not require_ssl:
require_ssl = force_ssl
if test_loader_name is None:
test_loader_name = inspect.stack()[1]
test_loader_name = os.path.splitext(os.path.basename(
test_loader_name[1]))[0]
# Initialize response handlers.
response_handlers = response_handlers or []
Extract suitemaking out of driver This creates a new module, suitemaker.py, which contains the code used to create a suite.GabbiSuite, which contains case.HTTPTestCase tests. This limits driver.py to being mostly code that is necessary to assemble the necessary information to create tests that are runnable by python test harnesses. This is distinguished from runner.py which assembles the necessary information to both create and _run_ tests itself. The idea here is that if the interface presented by test_suite_from_dict (both signature and that it returns a GabbiSuite) is preserved, then anything in suitemaker.py is welcome to change. The signature on test_suite_from_dict is the definition of what a caller (driver or runner or whatever else) needs to have learned: loader: the unittest.TestLoader which we might be able to default out of existence test_base_name: names help with test grouping so useful suite_dict: the main piece of the pie, the dict test_directory: the place where `data` can load files from host: the host any unqualified test goes to port: the port any unqualified test goes to fixture_module: the sole module from which fixtures come intercept: the wsgi app to intercept if any prefix: the url prefix host and intercept are mutually exclusive One can image it might be possible to replace host, port, prefix with a URL instead. If that were done than host and url would be mutually exclusive. If the signature of test_suite_from_dict changes then stuff in both driver and runner, in how they assemble the required info, would need to change. Note: For reasons unclear these changes have exposed some state management issues in test_runner, noted in a NOTE.
2016-06-03 15:07:57 +01:00
for handler in handlers.RESPONSE_HANDLERS + response_handlers:
handler(case.HTTPTestCase)
top_suite = suite.TestSuite()
for test_file in glob.iglob('%s/*.yaml' % path):
if intercept:
host = str(uuid.uuid4())
suite_dict = utils.load_yaml(yaml_file=test_file)
test_base_name = '%s_%s' % (
test_loader_name, os.path.splitext(os.path.basename(test_file))[0])
if require_ssl:
if 'defaults' in suite_dict:
suite_dict['defaults']['ssl'] = True
else:
suite_dict['defaults'] = {'ssl': True}
Extract suitemaking out of driver This creates a new module, suitemaker.py, which contains the code used to create a suite.GabbiSuite, which contains case.HTTPTestCase tests. This limits driver.py to being mostly code that is necessary to assemble the necessary information to create tests that are runnable by python test harnesses. This is distinguished from runner.py which assembles the necessary information to both create and _run_ tests itself. The idea here is that if the interface presented by test_suite_from_dict (both signature and that it returns a GabbiSuite) is preserved, then anything in suitemaker.py is welcome to change. The signature on test_suite_from_dict is the definition of what a caller (driver or runner or whatever else) needs to have learned: loader: the unittest.TestLoader which we might be able to default out of existence test_base_name: names help with test grouping so useful suite_dict: the main piece of the pie, the dict test_directory: the place where `data` can load files from host: the host any unqualified test goes to port: the port any unqualified test goes to fixture_module: the sole module from which fixtures come intercept: the wsgi app to intercept if any prefix: the url prefix host and intercept are mutually exclusive One can image it might be possible to replace host, port, prefix with a URL instead. If that were done than host and url would be mutually exclusive. If the signature of test_suite_from_dict changes then stuff in both driver and runner, in how they assemble the required info, would need to change. Note: For reasons unclear these changes have exposed some state management issues in test_runner, noted in a NOTE.
2016-06-03 15:07:57 +01:00
file_suite = suitemaker.test_suite_from_dict(
loader, test_base_name, suite_dict, path, host, port,
fixture_module, intercept, prefix)
top_suite.addTest(file_suite)
return top_suite
2014-12-15 13:33:00 +00:00
def py_test_generator(test_dir, host=None, port=8001, intercept=None,
prefix=None, test_loader_name=None,
fixture_module=None, response_handlers=None,
require_ssl=False, url=None):
"""Generate tests cases for py.test
This uses build_tests to create TestCases and then yields them in
a way that pytest can handle.
"""
loader = unittest.TestLoader()
result = reporter.PyTestResult()
tests = build_tests(test_dir, loader, host=host, port=port,
intercept=intercept,
test_loader_name=test_loader_name,
fixture_module=fixture_module,
response_handlers=response_handlers,
prefix=prefix, require_ssl=require_ssl,
url=url)
for test in tests:
if hasattr(test, '_tests'):
# Establish fixtures as if they were tests.
yield 'start_%s' % test._tests[0].__class__.__name__, \
test.start, result
for subtest in test:
yield '%s' % subtest.__class__.__name__, subtest, result
yield 'stop_%s' % test._tests[0].__class__.__name__, test.stop
def test_suite_from_yaml(loader, test_base_name, test_yaml, test_directory,
host, port, fixture_module, intercept, prefix=''):
"""Legacy wrapper retained for backwards compatibility."""
import warnings
with warnings.catch_warnings(): # ensures warnings filter is restored
warnings.simplefilter('default', DeprecationWarning)
warnings.warn('test_suite_from_yaml has been renamed to '
'test_suite_from_dict', DeprecationWarning, stacklevel=2)
Extract suitemaking out of driver This creates a new module, suitemaker.py, which contains the code used to create a suite.GabbiSuite, which contains case.HTTPTestCase tests. This limits driver.py to being mostly code that is necessary to assemble the necessary information to create tests that are runnable by python test harnesses. This is distinguished from runner.py which assembles the necessary information to both create and _run_ tests itself. The idea here is that if the interface presented by test_suite_from_dict (both signature and that it returns a GabbiSuite) is preserved, then anything in suitemaker.py is welcome to change. The signature on test_suite_from_dict is the definition of what a caller (driver or runner or whatever else) needs to have learned: loader: the unittest.TestLoader which we might be able to default out of existence test_base_name: names help with test grouping so useful suite_dict: the main piece of the pie, the dict test_directory: the place where `data` can load files from host: the host any unqualified test goes to port: the port any unqualified test goes to fixture_module: the sole module from which fixtures come intercept: the wsgi app to intercept if any prefix: the url prefix host and intercept are mutually exclusive One can image it might be possible to replace host, port, prefix with a URL instead. If that were done than host and url would be mutually exclusive. If the signature of test_suite_from_dict changes then stuff in both driver and runner, in how they assemble the required info, would need to change. Note: For reasons unclear these changes have exposed some state management issues in test_runner, noted in a NOTE.
2016-06-03 15:07:57 +01:00
return suitemaker.test_suite_from_dict(
loader, test_base_name, test_yaml, test_directory, host, port,
fixture_module, intercept, prefix)