Introduce test builds and unify testing tools interface

The general idea is that erlang.mk now keeps track of what kind
of build it generated. A test build is valid for all subsequent
test target invocations. A normal build is only valid for itself
and releases.

This rework adds the ability to specify deps to eunit.

The EUNIT_DIR variable is gone in favor of a more global TEST_DIR.

The tests-ct target got renamed to ct and documented.

Many more minor changes were done during the course of testing
these changes.

1 files changed, 8 insertions, 2 deletions

diff --git a/README.md b/README.md
index 8949a85..a2ee878 100644
--- a/README.md
+++ b/README.md
@@ -258,6 +258,9 @@ You can change compilation options by setting the `ERLC_OPTS`
 variable. It takes the arguments that will then be passed to
 `erlc`. For more information, please see `erl -man erlc`.
 
+Test target compilation options can be specified in `TEST_ERLC_OPTS`.
+It will override `ERLC_OPTS`.
+
 You can specify a list of modules to be compiled first using
 the `COMPILE_FIRST` variable.
 
@@ -331,7 +334,10 @@ The defaults are system dependent.
 Common_test plugin
 ------------------
 
-This plugin is available by default.
+This plugin is available by default. It adds the following
+target:
+
+`ct` runs all test suites for this application.
 
 There is nothing to configure to use it, simply create your
 test suites in the `./test/` directory and erlang.mk will
@@ -446,7 +452,7 @@ target:
 
 `eunit` which runs all the EUnit tests found in `ebin` and
 any of the additional EUnit directories specified in
-`EUNIT_DIR`.
+`TEST_DIR`.
 
 `EUNIT_OPTS` can be used to specify EUnit-specific options
 (e.g. `verbose`) that will be used when calling