Remove Elixir tests entry points as they were removed in december:

https://github.com/processone/ejabberd/commit/51cbbf313f478a01cd732a7ee1e21ff356402d0e#diff-098f6bcd4621d373cade4e832627b4f6

diff --git a/Makefile.in b/Makefile.in
index d3bcb282d2053154236967de9557869dacfbefef..1c3fbc204160eb2f46e47e076d6c7e8616446579 100644 (file)
--- a/Makefile.in
+++ b/Makefile.in
@@ -375,9 +375,6 @@ test:
        @cd priv && ln -sf ../sql
        $(REBAR) skip_deps=true ct
 
-quicktest:
-       $(REBAR) skip_deps=true ct suites=elixir
-
 .PHONY: src edoc dialyzer Makefile TAGS clean clean-rel distclean rel \
        install uninstall uninstall-binary uninstall-all translations deps test \
        quicktest erlang_plt deps_plt ejabberd_plt

diff --git a/test/README-quicktest.md b/test/README-quicktest.md
deleted file mode 100644 (file)
index 43c71e8..0000000
--- a/test/README-quicktest.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# Elixir unit tests
-
-## Running Elixir unit tests
-
-You can run Elixir unit tests with command:
-
-make quicktest
-
-You need to have ejabberd compile with Elixir and tools enabled.
-
-## Troubleshooting test
-
-To help with troubleshooting Elixir tests, we have added a special macro in ejabberd `logger.hrl` include file: ?EXUNIT_LOG
-
-To use this, in test file:
-
-1. in `setup_all, add:
-
-    ```
-    Application.start(:logger)
-    ```
-
-2. Enable log capture for the test you want to analyse by adding
-   `capture_log` tag before test implementation:
-
-   ```
-   @tag capture_log: true
-   ```
-
-In the ejabberd code, if `logger.hrl` is included, you can code adds a
-EXUNIT_LOG macro:
-
-    ?EXUNIT_LOG("My debug log:~p ~p", [Arg1, Arg2])