The APId tests are configured using one or more YAML files. These YAML files define what checks and what steps each check has to perform.

For more information on how to setup your environment, please follow our installation guide.

Introduction

An APId configuration file consists of variables and transactions which in turn consist of steps. Variables are pieces of data that can be referenced in multiple transactions. Steps are the basic elements of the configuration. They specify how to make a request and then how to validate its response. Transactions bundle steps together to help you represent meaningful stories.

Cloud specific configuration

Please refer to cloud reference.

Variables

APId has variables that can be inplaced throughout your steps and transactions. Variables can be declared for the transaction or step scope or be global. They can also come from the environment, which can be handy for things like secrets and passwords, or from a response from your API.

Variables are scoped either globally, to a transaction or to a step. Variables in a narrower scope have precedence over those in a broader one. Variables are available in templates - "{{ var.api_url }}". Make sure to add quotes to it so that the YAML parser doesn't confuse it for a YAML object.

Regular variables

These are declared either in the transaction, step or the root yaml document. There they are simply declared as a mapping from variable name to its value. Those will be available in templates using the var prefix - "{{ var.api_url }}"

Exported variables

Each step can export a set of variables. This is useful when you want to make a request and then use part of the response in another request. For example, when you authenticate to get a token and then use this token in subsequent requests. See step about the exact syntax of exporting variables in a step. Exported variables will be available in subsequent steps by using the step id that exported them; e.g "{{ step_one.auth_token }}"

Environment variables

These will contain anything environment variable that the APId CLI has inherited. Useful for injecting passwords or other kinds of secrets. They will be available like so: "{{ env.PASSWORD }}"

variables:
  title: "A long time ago"
  subtitle: "in a {{ var.place }} far far away {{ env.DATABASE_USER }} accidentally dropped all tables"
  year: 2187

Commands

Commands are a familiar way to manipulate variables. They allow you to run shell commands and use their output. There are practically no limitations as to what you can do.

The syntax for commands is very similar to the syntax of variables, but instead of using {{ and }} as as delimiters, it uses `

. For example{$ echo $ENV_VARIABLE $}`

Executables

Commands are executed in the default shell (defined in $SHELL), or /bin/sh if none is set.

CLI

You can use whatever commands you want, obviously you need to have them set up on you dev machine / build server.

Docker

The default docker image of APId is using alpine as the base image, therefore, it has very few executables pre-installed. If you need a more versatile docker image, feel free to build your own.

Using variables

You can use step and transaction variables from within commands. All the variables are exported for use in commands as $VAR_CAPITALIZEDNAMEOFVARIABLE, e.g if you want to use "{{ step_one.auth_token }}" in a command, you'd use `

. Another example might be, which will be available as

`. Note that dashes are replaced with underscores because most shells don't accept dashes inside variable names.

steps:
  request:
    endpoint: "{{ var.api_url }}/avengers/{% curl https://dynamic-avengers-api.io/random-avenger-id %}"

Configuration files

The configuration files are the single thing that defines your tests. You can have more than one config file, though in this case you need to provide the directory with config files to APId - apid check -c /dir/to/configs/. When providing multiple config files you can reference root variables defined in other files, however you can't reference transactions from other files.

Transaction

A transaction is a list of steps which are executed sequentially. If a step fails, the whole transaction and the other steps in the transaction are not executed.

id: "transaction-one"
variables:
  api_url: "https://jsonplaceholder.typicode.com"
steps:
  - id: "todos-1"
    request:
      method: "GET"
      endpoint: "{{ var.api_url }}/todos/1"

Matrix

A matrix allows running the same transaction with different variables. Different combinations of the variables will be generated and the transaction will be ran with all of them. The order in which they are generated is not guaranteed.

The below will send four different requests in four different transactions.

id: transaction
matrix:
  api_url:
    - "http://localhost:8080"
    - "https://jsonplaceholder.typicode.com"
  todo_id:
    - 1
    - 2
steps:
  - id: todos
    request:
      method: GET
      endpoint: "{{ var.api_url }}/todos/{{ var.todo_id }}"

The different transactions and requests:

• todos-1: GET http://localhost:8080/todos/1

• todos-2: GET http://localhost:8080/todos/2

• todos-3: GET https://jsonplaceholder.typicode.com/todos/1

• todos-4: GET https://jsonplaceholder.typicode.com/todos/2

Step

A step is a call to a single endpoint with optional validation of the response.

steps:
  - id: "get user with id 1"
    variables:
      api_url: "http://localhost:80"
    request:
      method: "GET"
      endpoint: "{{ var.api_url }}/users/1"
    expect:
      code: 200
      body:
        type: "json"
        content: |
          {
            "first_name": "Bobby",
            "last_name": "Hounslow",
            "address": {
                "postcode": "TW4 7AE",
                "country": "UK",
            }
          }
    export:
      auth_header: "response.headers.X-APIDAUTH"
      auth_token: "response.body.access_token"

Request

Request specifies what request to make - which endpoint to go to, what body to use, etc.

request:
  method: "GET"
  endpoint: "http://https://jsonplaceholder.typicode.com/posts/1"
  headers:
    X-APIDAUTH: "{{ env.AUTH_TOKEN }}"
    Accept: "application/json"
    Accept: "application/ld+json"
    Accept:
      - "application/json"
      - "application/ld+json"

Expect

Expect will define what we are expecting as a valid response from the API.

expect:
  code: 200
  headers:
    Accept: "application/json"

Body

Body provides a bit more flexibility on what body to expect in this response.

expect:
  body:
    - is: |
        {
          "name": {"first": "Tom", "last": "Anderson"},
          "age":37,
          "children": ["Sara","Alex","Jack"],
          "fav.movie": "Deer Hunter",
          "friends": [
            {"first": "Dale", "last": "Murphy", "age": 44, "nets": ["ig", "fb", "tw"]},
            {"first": "Roger", "last": "Craig", "age": 68, "nets": ["fb", "tw"]},
            {"first": "Jane", "last": "Murphy", "age": 47, "nets": ["ig", "tw"]}
          ]
        }
    - selector: name
      is: |
        {
          "first": "Tom", 
          "last": "Anderson"
        }
​
    - selector: name
      keys_only: true
      is: |
        {
          "first": "Something, but not Tom", 
          "last": "not Anderson"
        }
​
    - selector: name
      subset: true
      keys_only: true
      is: |
        {
          "first": "Something, but not Tom"
        }
​
    - selector: name
      subset: true
      is: |
        {
          "first": "Tom"
        }
​
    - selector: friends.#.first
      is: |
        [
          "Dale",
          "Jane",
          "Roger"
        ]
​
    - selector: friends.#.first
      subset: true
      is: |
        [
          "Rojer"
        ]

Skip SSL verification

SSL verification can be skipped on all steps in a APId config (suite). Specify the skip_ssl_verify: True field at the root of the config and it will be applied to all steps. If a step has that field specified already, the step's field will take precedence.