ltest
ltest copied to clipboard
lfex
A Testing Framework for LFE (successor to lfeunit)
Still all test modules are run.
`rebar3 as test lfe ltest` has a shell exit of 0, indicating no error. but `rebar3 eunit` returns with != 0, indicating error.
Tasks: * [ ] As with the lanes project, let's use mdbook for this (update `Makefile`, etc.) * [ ] Move documentation content out of README * [ ] Keep...
There are places in ltest that have to do some very ugly destructuring: * https://github.com/lfex/ltest/blob/ff9d44e312c82af7a7096689e435c7567eeb1f71/src/ltest.lfe#L146 This is due to Erlang having some pretty ugly (also probably quite old) error-creation for...
Right now, each run of eunit only knows about its own state. What we want is a mechanism for tracking state of all eunit runs, not just the one that's...
Note: Also created this ticket in the test runner project: https://github.com/lfe-rebar3/test/issues/2 When running the unit tests for the kanin project (see https://github.com/lfex/kanin/blob/master/test/unit-kanin-uri-tests.lfe), an error arises (unspecified ... looks like an...
Sadly, EUnit states are undocumented. The source code has to be examined when attempting to create a 100% EUnit compatible test listener. The following files need to be compared carefully:...