[erlang-questions] TDD, Erlang and Emacs
Fabrice Nourisson
fabrice.nourisson@REDACTED
Fri Mar 2 10:27:16 CET 2012
Hi,
I use Active-Ring (https://github.com/extremeforge/active-ring) to
develop in TDD with Erlang and Emacs.
In normal use my emacs's screen is split into 3 parts
- one for the test module
- one for the tested module
- one for the continuous test results
In this depot there is an emacs-plugin to run the test in emacs. This
plugin bind the emacs's compile command to run tests into emacs.
For more information you could read the README.
Fabrice Nourisson
Le 02/03/2012 00:24, Jayson Barley a écrit :
> I am wondering if anyone has any recommendations for a smoother TDD
> experience with Erlang and Emacs. I am finding the process to be less
> than optimal. The way I am doing it now is that I have 3 windows open.
>
> 1. In my test module I write my test
> 2. Switch to the Erlang buffer
> 3. Run my tests, see that it fails
> 4. Switch to the module under test buffer, write code to get the
> test to pass
> 5. Switch back to the Erlang buffer, run my tests again
> 6. Switch back to the test buffer and repeat.
>
> Ideally I would like to have 2 windows open, 1 for the module under
> test and the other for the test window. From the module under test
> buffer or the test module I should be able to run the tests, see that
> they pass or fail and then move on.I have been considering writing an
> plugin to handle this functionality for me. Before I go that route I
> want to make sure I am not duplicating what someone else has already done.
>
> Does anyone have any recommendations for how to do this better?
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120302/0b1ff20c/attachment.htm>
More information about the erlang-questions
mailing list