Closed oubiwann closed 10 years ago
Oddly, when creating a library project from scratch, lfetool tests all
and make check
work without issue...
Looks like it works when using the old lunit but not the newer ltest.
Part of a fix for this was done here: 124107e9fd71a3bedb3fd303b7366933cac8b63c
The related adjustment was made here: https://github.com/lfex/ltest/commit/eeacfeb3103ee96871c9cb2824edc3ffa14c7ead
Hrm, curiousor and curiousor ... manual execution of the bits of Erlang code that are stitched together by lfetool to run the tests, actually works. So possibly something's gone wrong with the stitching as a result of using ltest and lutil?
Not really close to a solution, but I did comment all the Erlang code out in the unit test runner portion of lfetool, and it's still throwing an error. So I'm overlooking something -- that's a little bit of good news :-) If I wasn't overlooking anything, I wouldn't have any ideas!
Ah, freakin' other lfetools in the $PATH. Damn.
Okay! That was it :-) Looks like the code fix from the last commit did in fact do the trick :-)
Even with the expected directory structure in the old tests (test/unit, test/integration, test/system), it's still not working. It should work in that system as well as the new one (flat directory structure in test).