| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
This defvar was removed in a87a9699735b0a25f99397fba9576f5756da54d3 which made
eunit fail on running tests in emacs.
|
|
Follow the GNU recommendation of not introducing runtime
dependencies on the Common Lisp package in ELisp packages
that will be distributed for widespread use.
In practice this means it's ok to use cl macros but not
functions.
|
|
This determines the most recent invocation of EUnit and runs it
again -- whether one test or all tests in a module were run (and
if all a module's tests were run, whether cover compilation was
involved). This can be especially handy when one test is being
run repeatedly, eliminating the need to position the cursor in
the desired test just to run it.
Default keybinding: C-c C-e l
|
|
If the variable 'erlang-eunit-autosave' is non-nil, buffers will be
automatically saved just before running tests -- the "Do you want
to save?" prompt will be inhibited. This can be useful, reducing the
save-compile-load-test cycle to just one keychord.
|
|
Add a number of features to the emacs mode which make it easier to
work with eunit test cases while keeping track of code coverage.
* C-cC-ec:
Compile the module under test for code coverage analysis, run tests
and show the results of the coverage analysis in a new buffer.
* C-c-C-ev:
Compile the current module for code coverage analysis.
* C-cC-ea:
Show the results of the coverage analysis in a new buffer.
|
|
Previously there were only two options: either the EUnit test file was
placed directly within the test directory or within the same directory
as the source file. Now a list of candidate locations are supported.
This way more than two alternative locations are supported as well as
arbitrarily deep directory structures (i.e. test/eunit/x_tests.erl).
The default behaviour is still the same, but it's possible to specify
locations by setting the following two variables:
erlang-eunit-src-candidate-dirs
erlang-eunit-test-candidate-dirs
|
|
* cb/emacs-eunit-run-current-test:
Add Emacs EUnit utility feature: run current test function.
|
|
This determines the current test function under point (cursor), whether the active buffer
contains a test module (foo_tests) or the module itself (foo), then compiles the source
module (and test module if present) and runs that test function.
Since this added a third testing feature, there was some natural duplication that needed
to be factored out. The notion of 'compile and run tests' was decoupled from exactly
which tests should be run. The definitions of default keybindings were converted to a list
for clarity and conciseness.
|
|
* rd/erlang-eunit:
erlang-eunit.el: Require cl, as it is used
|
|
erlang-eunit.el (part of erlang-mode) uses "flet", which is only available
if emacs package cl was loaded. The docs of the CL package suggest that
'...packages installed in Emacs must not load "CL" at run time.' We
honour this by using eval-when-compile.
This fixes warnings when byte-compiling erlang-eunit.el with:
emacs -batch -f batch-byte-compile erlang-eunit.el
The warning fixed is:
In erlang-eunit-compile-and-run-tests:
erlang-eunit.el:146:4:Warning: `(save-some-buffers (&optional any) nil)'
is a malformed function
This bug was reported initially against Ubuntu packages, see
https://bugs.launchpad.net/bugs/541893 for reference
Signed-off-by: Ralf Doering <[email protected]>
|
|
|
