Traffic Server Blackbox Testing

Traffic Server uses the Reusable Gold Testing System (AuTest) for functional testing. The current layout is:

gold_tests/ - contains all the tests that run on the Reusable Gold Testing System (AuTest)
tools/ - contains programs used to help with testing.


To ease the process of running Autest, there is and - This file is a simple wrapper that will call the Reusable Gold Testing System (Autest) program in a pipenv. If the pipenv is not setup, the script will prompt user the missing components. That will set up the Autest on most systems in a Python virtual environment. The wrapper adds some basic options to the command to point to the location of the tests. Run the script from the tests/ directory followed by --ats-bin and the bin directory where ATS is located (e.g. ~/ats/bin) Use --help for more details on options for running Autest. - This script will check for the necessary packages needed to create a pipenv that can run Autest. If any package is missing, the script will alert the user. If all packages are available, it will install a virtual environment using the provided Pipfile.

Manual Setup

To run autest manually, the recommended way is to follow these steps:

  1. pipenv install: create the virtual environment(only needed once).

  2. pipenv shell: enter a shell in the virtual environment(type exit to leave the shell).

  3. cd gold_tests: enter the directory containing the test files.

  4. autest --ats-bin user_ats_bin: run autest where user_ats_bin is the bin directory in the user’s ats directory.

Advanced Setup

AuTest and the relevant tools can be install manually instead of using the wrapper script. By doing this, it is often easier to debug issues with the testing system, or the tests. There are two ways this can be done.

  1. Run the bootstrap script then source the path with a source ./env-test/bin/activate command. At this point autest command should run without the wrapper script.

  2. Make sure you install python 3.5 or better on your system. From there install these python packages (e.g. pip install):

Writing Tests

When writing tests, please refer to the current documentation for general use of the Autest system.

Testing Environment

The environment of the testing process will have a number of added environment variables to control Traffic Server running the in the sandbox location correctly. This can be used to easily setup other commands that should run under same environment.

Autest Extensions

Autest allows the user to create extensions to help specialize and simplify test writing for a given application domain.


For TrafficServer, we have defined the following functions and objects in tests/gold_tests/autest-site/trafficserver.test.ext:

  • MakeATSProcess(obj, name, command='traffic_server', enable_tls=False)

    • name - A name for this instance of ATS

    • command - optional argument defining what process to use. Defaults to traffic_server

    • select_ports - have Autest automatically select a nonSSL port to use

    • enable_tls - have Autest automatically select SSL port (select_ports must be True)

  • CopyConfig(file, targetname=None, process=None)

    • file - name of the file to copy. Relative paths are relative from the test file location

    • targetname - the name of the file when copied to the correct configuration location

    • process - optional process object to use for getting path location to copy to. Only needed if the Setup object call is not in the scope of the process object created with the MakeATSProcess(…) API.

This function copies a given configuration file to the location of the Traffic Server sandbox used in a test. Given a test might have more than on Traffic Server instance, it can be difficult to understand the correct location to copy to. This function will deal with the details correctly.

When automatically selected, the following ports will be allocated for TS:

  • port

  • portv6

  • ssl_port

  • admin_port - this is set even if select_port is False

A number of file objects are also defined to help test TrafficServer. Files that are currently defined are:

  • squid.log

  • error.log

  • diags.log

  • records.yaml

  • cache.config

  • hosting.config

  • ip_allow.yaml

  • logging.yaml

  • parent.config

  • plugin.config

  • remap.config

  • sni.yaml

  • socks.config

  • splitdns.config

  • ssl_multicert.config

  • storage.config

  • volume.config

ts1 = Test.MakeATSProcess("ts1",select_ports=False)
# uses the setup object in the scope of the process object

Origin Server

  • Test.MakeOriginServer(name, port, s_port, ip, delay, ssl, lookup_key, clientcert, clientkey)

    • name - A name for this instance of origin server.

    • port - option to specify the nonSSL port. If left unspecified, the port will be autoselected.

    • s_port - option to specify the SSL port. If left unspecified, the port will be autoselected (SSL has to be True).

    • ip - option to specify IP address. Defaults to

    • delay - option to have MicroServer delay for set amount of seconds before returning response. Defaults to 0.

    • ssl - option to enable SSL

    • lookup_key - option to change the unique identifier that MicroServer uses to identify each transaction. Defaults to PATH.

    • clientcert - path to cert used for SSL. Defaults to the included cert in tests/tools/microserver/ssl.

    • clientkey - path to key used for SSL. Same default as above.

This function returns a AuTest process object that launches the python-based Microserver. Microserver is a mock server which responds to client http requests. Microserver needs to be setup for the tests that require an origin server behind ATS. The server reads a JSON-formatted data file that contains request headers and the corresponding response headers. Microserver responds with payload if the response header contains Content-Length or Transfer-Encoding specified.

  • Test.addResponse(filename, request_header, response_header)

    • filename - name of the file where the request header and response header will be written to in JSON format

    • request_header - dictionary of request header

    • response_header - dictionary of response header corresponding to the request header.

This function adds the request header and response header to a file which is then read by the microserver to populate request-response map. The key-fields required for the header dictionary are ‘headers’, ‘timestamp’ and ‘body’.

# create the origin server process
# define the request header and the desired response header
request_header={"headers": "GET / HTTP/1.1\r\nHost:\r\n\r\n", "timestamp": "1469733493.993", "body": ""}
# desired response form the origin server
response_header={"headers": "HTTP/1.1 200 OK\r\nConnection: close\r\n\r\n", "timestamp": "1469733493.993", "body": ""}
# addResponse adds the transaction to a file which is used by the server
server.addResponse("sessionlog.json", request_header, response_header)


  • Test.MakeDNServer(name, filename, port, ip, rr, default)

    • name - A name for this instance of MicroDNS.

    • filename - file containing zone information for MicroDNS to read from. Defaults to dns_file.json

    • port - option for the DNS port. Autoselected if left unspecified.

    • ip - option for IP address. Defaults to

    • rr - option to enable round robin IP. Defaults to False

    • default - option to specify a default IP response when MicroDNS can’t find a domain:IP pair.

  • dns.addRecords(records, jsonFile)

    • records - a dictionary of domain:IP mappings in the form of {"domain A": [IP1, IP2], "domain B": [IP3, IP4]}

    • jsonFile - a JSON file containing domain:IP mappings

The JSON file must take the form of

  "mappings: [
      {"domain A": [IP1, IP2]},
      {"domain B": [IP3, IP4]}
# If everything is mapped to
dns = Test.MakeDNServer("dns", default=[''])
# Using addRecords method
dns = Test.MakeDNServer("dns")

dns.addRecords(records={"":["", ""]})
dns.addRecords(jsonFile="zone.json") # where zone.json is in the format described above
Condition Testing
  • Condition.HasCurlFeature(feature)

    This function tests Curl for possible features it has been compiled with. Consult Curl documentation for possible features.

  • Condition.PluginExists(pluginname)

    This function tests for the existence of a certain plugin in ATS.

  • Condition.HasATSFeature(feature)

    This function tests TrafficServer for possible features it has been compiled with. Current features you can test for are:

















    • TS_USE_TLS13





    • TS_HAS_128BIT_CAS