From ef1a75a6287c92f942f272d4395043a9c42c28e7 Mon Sep 17 00:00:00 2001 From: Mickael Remond Date: Wed, 1 May 2019 11:51:17 +0200 Subject: [PATCH] Remove Elixir tests entry points as they were removed in december: https://github.com/processone/ejabberd/commit/51cbbf313f478a01cd732a7ee1e21ff356402d0e#diff-098f6bcd4621d373cade4e832627b4f6 --- Makefile.in | 3 --- test/README-quicktest.md | 33 --------------------------------- 2 files changed, 36 deletions(-) delete mode 100644 test/README-quicktest.md diff --git a/Makefile.in b/Makefile.in index d3bcb282d..1c3fbc204 100644 --- 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 index 43c71e86b..000000000 --- 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]) -- 2.50.1