| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
The format of stacktraces was changed in Erlang/OTP R15, adding location
information. This had the effect that EUnit did not recognize stack traces
as such and only printed the exception term. This patch makes Eunit
recognize and print the new stacktrace format as well as the old.
|
|
|
|
OTP-10106
OTP-10107
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* rc/eunit-2.2.0:
Updated to EUnit version 2.2.0
OTP-9505
|
|
New macros assertNotMatch(Guard, Expr), assertNotEqual(Unexpected, Expr),
and assertNotException(Class, Term, Expr).
The debugMsg macro now also prints the pid of the current process.
When testing all modules in a directory, tests in <Module>_tests.erl are
no longer executed twice.
The use of 'regexp' internally has been replaced with 're'.
|
|
|
|
|
|
Previously the test cases of all test suites (=modules) were put in
one and the same surefire report XML thereby breaking the principle of
least astonishment and making post analysis harder. Assume the
following layout:
src/x.erl
src/y.erl
test/x_tests.erl
test/y_tests.erl
The results for both x_tests and y_tests were written to only one
report grouped under either module x or y (seemingly randomly).
Now two reports, one for module x and one for y are generated.
|
|
When eunit is terminating, a stop message is sent to all listeners and
eunit then waits for *one* result message but previously both
eunit_tty and eunit_surefire sent a response on error. Don't send a
result message from eunit_surefire; let eunit_tty take care of all
result reporting, both positive and negative to avoid race conditions
and inconsistencies.
|
|
Ensure that all eunit listeners (like eunit_surefire) get the chance
to finish their work before terminating. Prior to this fix, the
eunit_surefire XML was sometimes not generated.
|
|
Currently, error messages in Eunit Surefire reports are shortened just
like when written to a terminal. However, the space limitations that
constrain terminal output do not apply here, so it's more useful to
include more of the error message. Getting the full error message can
be particularly helpful when an assertMatch fails because of a long
and deep error term.
The new depth of 100 should be enough for most cases, while protecting
against runaway errors.
|
|
warnings/errors in man pages
|
|
|
