| Age | Commit message (Collapse) | Author |
|---|
|
The surefire reports get called `TEXT-file_"foo.app".xml`, which creates all sorts of problems in the shell. I suggest that double quotes are removed like the single ones.
|
|
This makes it clear that Apache 2.0 applies, without dropping the old LGPL
licensing, and makes all the EUnit file headers look the same as upstream.
|
|
A record field type has been modified due to commit 8ce35b2:
"Take out automatic insertion of 'undefined' from typed record fields".
|
|
* richcarl/eunit-2.2.10:
bumped revision
clean up a comment
Improve surefire xml <testcase> element
Conflicts:
lib/eunit/src/eunit_surefire.erl
lib/eunit/vsn.mk
|
|
All output from eunit is unicode, including the surefire XML files.
|
|
Remove the 'description' attribute. It is not generated by Apache
Ant or Maven Surefire and probably ignored by all other Surefire
tools. Confirmed for Jenkins.
Add testcase description (if there is one) to the 'name' attribute.
Change format of 'name' attribute to look more like the output from
running eunit with verbose. Line number and arity was quite obscure
and arity is not useful as it is always 0.
|
|
|
|
This is to avoid outputting something like "\"%\f" instead of [34,37,12] in the XML.
|
|
|
|
|
|
An error during fixture setup means that some tests could not be run,
and therefore needs to be highlighted in the test report. Likewise, a
cleanup failure is often a problem that needs to be looked into.
Since setup and cleanup are not part of any single test in Eunit's
view, I include them as phantom test cases in the report whenever they
fail.
|
|
|
|
|
|
|
|
|
|
* 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.
|
|
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
|
|
|
