You are browsing documentation for an outdated version. See the latest documentation here.

Writing tests

If you are serious about your plugin, you probably want to write tests for it. Unit testing Lua is easy, and many testing frameworks are available. However, you might also want to write integration tests. Again, Kong has your back.

Write integration tests

The preferred testing framework for Kong is busted running with the resty-cli interpreter, though you are free to use a different one. In the Kong repository, the busted executable can be found at bin/busted.

Kong provides you with a helper to start and stop it from Lua in your test suite: spec.helpers. This helper also provides you with ways to insert fixtures in your datastore before running your tests, as well as dropping it, and various other helpers.

If you are writing your plugin in your own repository, you will need to copy the following files until the Kong testing framework is released:

  • bin/busted: the busted executable running with the resty-cli interpreter
  • spec/helpers.lua: helper functions to start/stop Kong from busted
  • spec/kong_tests.conf: a configuration file for your running your test Kong instances with the helpers module

Assuming that the spec.helpers module is available in your LUA_PATH, you can use the following Lua code in busted to start and stop Kong:

  1. local helpers = require "spec.helpers"
  3. for _, strategy in helpers.each_strategy() do
  4.   describe("my plugin", function()
  6.     local bp = helpers.get_db_utils(strategy)
  8.     setup(function()
  9.       local service = bp.services:insert {
  10.         name = "test-service",
  11.         host = "httpbin.org"
  12.       }
  14.       bp.routes:insert({
  15.         hosts = { "test.com" },
  16.         service = { id = service.id }
  17.       })
  19.       -- start Kong with your testing Kong configuration (defined in "spec.helpers")
  20.       assert(helpers.start_kong( { plugins = "bundled,my-plugin" }))
  22.       admin_client = helpers.admin_client()
  23.     end)
  25.     teardown(function()
  26.       if admin_client then
  27.         admin_client:close()
  28.       end
  30.       helpers.stop_kong()
  31.     end)
  33.     before_each(function()
  34.       proxy_client = helpers.proxy_client()
  35.     end)
  37.     after_each(function()
  38.       if proxy_client then
  39.         proxy_client:close()
  40.       end
  41.     end)
  43.     describe("thing", function()
  44.       it("should do thing", function()
  45.         -- send requests through Kong
  46.         local res = proxy_client:get("/get", {
  47.           headers = {
  48.             ["Host"] = "test.com"
  49.           }
  50.         })
  52.         local body = assert.res_status(200, res)
  54.         -- body is a string containing the response
  55.       end)
  56.     end)
  57.   end)
  58. end

With the test Kong configuration file, Kong is running with its proxy listening on port 9000 (HTTP), 9443 (HTTPS) and Admin API on port 9001.

For a real-world example, see the Key-Auth plugin specs.

Previous Extending the Admin API

Next (un)Installing your plugin