-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elixir support? #127
Comments
Hi @brbrr, Did you have a chance to read this [1] part of README file? Hope the information there will help you. [1]. https://github.com/esl/escalus#escalus-as-a-standalone-application |
ok, thanks! I'll try to use it. btw, is it correct place to ask questions? |
This is the right place to ask questions. You can use function Getting back to your initial problem. You basically would like to add a new test suite but write it in Elixir instead of Erlang? |
Yeah, I wanted to use Elixir to write some tests for custom mongoose server(custom registration, message delivery etc). I was thinking about Elixir just because im new for both elixir and erlang, and elixir looks kinda easier to get in to. But if I want to use custom modules - I need to use erlang... So I started to use erlang, and make gears to spin a little, but now Im stuck on other problem. |
I think |
UPD: ah, its because init_per_group uses different process than test cases itself. was managed to workaround with: http://stackoverflow.com/a/15634582/3078381 Thanks! This will work:
This wont:
|
Hi,
Im new to erlang and elixir, so sorry for (maybe) obvious question.
Is it possible to use Escalus on elixir project? Im planning to write some tests for custom functionality in MongooseIM, but I prefer Elixir over Erlang because of the ruby like syntax etc.
Im kinda stuck on getting config file:
Escalus will look in to wrong dir(I insert
erlang:display(Path)
in toescalus_ct.erl:50
):/Users/brbrr/Development/Vega/eliTests/_build/test/lib/escalus/test/test.config
instead of/Users/brbrr/Development/Vega/eliTests/test/test.config
The text was updated successfully, but these errors were encountered: