kanban for veritas

To-do

( 9 )

Add JSON reporter, XML reporter and more

Syntax Ergonomics: Macro-Driven Lazy Evaluation

XML and CI/CD Friendly Reporters

State-Passing Fixtures (Setup/Teardown Context)

Diff show pretty why an assert fails, diff between lists or strings for example

Timeout to suites and to tests

html file reporter

Add assert-match: pattern matching assertion super-power

Add more generators for useful patterns and add fake data (fake names, beers, cars, etc.)

Work in Progress

( 2 )

Native Property-Based Testing (PBT)

How to measure code coverage? and how to report it?

In Review

( 0 )

Done

( 20 )

Fix the Runner's Directory Depth Limit

Richer Assertion Library (Pattern Matching & Floats)

before, after each all with hooks a la Emacs

reports

choice of reporter can be via env variable

rackunit inspiration and reporting, asserts

feedback #1

testworks dylan inspiration reporting, asserts naming

test runner allow testing only things that match the name partially like in sbt testOnly *something*

benchmarking capabilities

test runner to auto discover files and to launch nicely

create good documentation, also in html / org mode for veritas api

add time taken for suites and for whole thing

record types for suites, test and assertion results

support running suites and tests mixed, also only suites, or only tests

fix assertion succesful collection nicely

configurable concurrent suite, and test, with fibers

add test and suite skips

shuffle suite, test and assertions

setup foundations


Rejected

( 1 )

add line number on err