Unit testing of asynchrononous code in Nim
Go to file
Mark Spanbroek 1ecce5d1a6 Update documentation for setupAll and teardownAll 2022-03-01 09:25:15 +01:00
.github/workflows Run CI also on older version of Nim 2021-07-07 10:36:37 +02:00
asynctest Update documentation for setupAll and teardownAll 2022-03-01 09:25:15 +01:00
testmodules feat: add support for suite before and after 2022-03-01 07:22:46 +01:00
.editorconfig Asynchronous testing in Nim 2021-01-11 13:35:19 +01:00
.gitignore Asynchronous testing in Nim 2021-01-11 13:35:19 +01:00
.tool-versions Nim 1.4.8 2021-07-07 10:33:52 +02:00
License.md Add license 2022-01-10 11:14:39 +01:00
Readme.md Update documentation for setupAll and teardownAll 2022-03-01 09:25:15 +01:00
asynctest.nim Add support for unittest2 2021-07-07 10:33:52 +02:00
asynctest.nimble version 0.3.0 2021-07-07 10:33:52 +02:00

Readme.md

asynctest

Complements the standard unittest module in Nim to allow testing of asynchronous code.

Installation

Use the Nimble package manager to add asynctest to an existing project. Add the following to its .nimble file:

requires "asynctest >= 0.3.0 & < 0.4.0"

Usage

Simply replace import unittest with import asynctest, and you can await asynchronous calls in tests, setup and teardown.

Example


import asynctest
import asyncdispatch # alternatively: import chronos

proc someAsyncProc {.async.} =
  # perform some async operations using await

suite "test async proc":

  setup:
    # invoke await in each test setup:
    await someAsyncProc()

  teardown:
    # invoke await in each test teardown:
    await someAsyncProc()

  test "async test":
    # invoke await in tests:
    await someAsyncProc()

setupAll and teardownAll

The setup and teardown code runs before and after every test, just like the standard unittest module. In addition we provide setupAll and teardownAll. The setupAll code runs once before all tests in the suite, and the teardownAll runs once after all tests in the suite. Use these only as a last resort when setting up the test environment is very costly. Be careful that the tests do not modify the environment that you set up, lest you introduce dependencies between tests.

Unittest2

The unittest2 package is supported. Make sure that you import asynctest/unittest2 instead of the normal import.