yetangitu/ejabberd
1
0
Fork 0
mirror of https://github.com/processone/ejabberd synced 2025-10-03 09:49:18 +02:00
Code Issues Releases Wiki Activity

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

Browse source 
51cbbf313f (diff-098f6bcd4621d373cade4e832627b4f6)
This commit is contained in:
Mickael Remond 2019-05-01 11:51:17 +02:00
parent 7eb5a0877b
commit ef1a75a628
No known key found for this signature in database
GPG key ID: 40C24F21D564358A
2 changed files with 0 additions and 36 deletions
Download patch file Download diff file Expand all files Collapse all files

3
Makefile.in
View file

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

33
test/README-quicktest.md
View file

@ -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])