Skip to content

Latest commit

 

History

History
151 lines (106 loc) · 4.03 KB

README.md

File metadata and controls

151 lines (106 loc) · 4.03 KB
Raw

luatest

codecov

A Lua test runner

Lua has a handful of test runners like Busted. These tools are good, but the ones that I've encountered use a BDD-style. My preferences have moved away from BDD-style runners (for reasons that I may document elsewhere at a later time).

The goal of this test runner is provide a fairly opinionated test runner in the style of pytest for Python. The feature set will be highly constrained initially to satisfy my use cases and keep maintenance light.

Assertion functionality is delegated to luassert.

$ luatest
Collected 24 tests

tests/test_collection.lua .....
tests/test_coverage.lua .
tests/test_executor.lua ..
tests/test_reporter.lua ................

24 passed in 0.0s

Install

luarocks install luatest

Features

  1. Discover, collect, and execute test code.
  2. Measure code coverage via luacov.

Test filtering

You can execute a subset of your test suite by using positional arguments to luatest. These arguments can be in one of three forms, and these forms can be used in combination. The three forms are:

  1. A directory within the test suite will collect tests within that directory.
  2. A test file within the test suite will collect all tests within that file.
  3. A test file with a test name, separated by ::, will collect an individual test.

Here's an example invocation (using verbose output) from luatest's own test suite to illustrate.

$ luatest --verbose \
    tests/test_executor.lua \
    tests/test_collection.lua::test_collects_test_modules
Searching /Users/matt/projects/luatest/tests
Collected 3 tests

tests/test_collection.lua::test_collects_test_modules PASSED
tests/test_executor.lua::test_fail PASSED
tests/test_executor.lua::test_pass PASSED

3 passed in 0.0s

stdout/stderr capturing

By default, luatest will attempt to capture any usage of stdout and stderr via io.stdout, io.stderr, or print. Anything captured during test exeuction will be stored upon failures and displayed with assertion detail diagnostics.

To disable this behavior, use the --no-capture flag.

Configuration

luatest checks for configuration from two sources:

  1. Command line flags
  2. A configuration file named luaproject.toml

Command line flags

See luatest -h for the full list of all available flags.

  • --cov - Use this flag to measure code coverage for a given directory.
  • --no-capture - Use this flag to disable stdout/stderr capturing.

Configuration file

The luaproject.toml example is shown below with inline comments to explain the supported configuration. Each configuration value shows the default configuration.

# All configuration options are under the tool.luatest table.
[tool.luatest]

# The directory to search when looking for tests.
tests_dir = "tests"

# The pattern that will be used to discover test modules.
# This default pattern will match a file that looks like "test_<something>.lua".
test_file_pattern = "test_.+%.lua"

Test files

By default, luatest will search for files in a top-level tests directory. A test file should be standard Lua module. luatest will execute every function that is added to the test file's module table.

This is an example file to show what your test module may look like. Assume that this file is tests/test_example.lua

local assert = require "luassert"

local my_module = require "my_module"

local tests = {}

-- my_func answers the meaning of life.
function tests.test_my_func()
    local meaning_of_life = my_module.my_func()

    assert.is_equal(42, meaning_of_life)
end

return tests

Making releases

These are notes to help me remember how to cut a release for LuaRocks.

luarocks new_version luatest-dev-1.rockspec <new version like 0.2>
# Upload expects branch name of v0.1 format
git tag -a v0.2 -m 0.2
# The upload command will build a source rock locally.
# Example
luarocks upload rockspecs/luatest-0.1-1.rockspec --api-key=$LUAROCKS_KEY