diff options
author | Chris Bernard <cebernard@gmail.com> | 2010-03-04 20:53:12 -0500 |
---|---|---|
committer | Chris Bernard <cebernard@gmail.com> | 2010-03-04 20:53:12 -0500 |
commit | 25538e071fa154b49a8f282e84907316b1bf54b6 (patch) | |
tree | 7bfe9249f669b3137711c71b8bd7231360e0f643 /priv/shell-completion | |
parent | 56e30351f70dc9924ff873fc4fbb1e9738c807d2 (diff) |
Fixed 3 bugs in rebar_eunit. Added EUnit tests to capture them.
1. When running the eunit command with the convention of putting
tests in "*_tests" modules, eunit would run those tests twice. This
is because: 1) eunit:test/1 will naturally look for foo's tests both
in foo, and in foo_tests, and 2) eunit:test/1 was being folded over
all project modules. The fix is to filter "*_tests" modules from the
list passed to eunit:test/1.
2. When running the eunit command with cover enabled and tests in a
'test' directory, cover would error because it couldn't find the
source code for those tests. This is because cover:analyze/3 will
only find module source in "." and "../src". This is hard-coded in
cover :-(. Since cover shouldn't be calculating code coverage on test
code anyway, the fix is to not fold cover:analyze/3 over
non-production code.
3. When running the eunit command with cover enabled and a test suite
defined, cover would only attempt to calculate coverage on the the
test suite itself. This was because only the suite was passed to
cover:analyze/3. The fix is to fold cover:analyze/3 over all the
production code, filtering out the suite module if it is defined.
Diffstat (limited to 'priv/shell-completion')
0 files changed, 0 insertions, 0 deletions