gmane.comp.programming.extreme-programming.extremeforge.devel

Re: Eunit support

Nicolas Charpentier — 2011-08-30T06:19:27

Hi,

My first thought ws to use parse_transform to detect eunit tests at compilation and generate the correct wrapper.
The simple cases are quite easy to handle, however if the tests are strange it will become tricky as the parse_transform has to detect the return value of the generator .....
Maybe that this idea wasn't the best one, a wrapper seems to be simpler.

Question: After that ActiveRing has started to execute the tests, can it advice the world that there is more test ? 

Cheers,
Nicolas


On 20 Aug 2011, at 08:06, Nicolas Charpentier wrote:

Eunit support

Nicolas Charpentier — 2011-08-20T07:06:24

Hi,

I started a spike to see how to support eunit tests in extremeforge, =
oups.... activering.

The code can be found on github =
https://github.com/charpi/active-ring/tree/eunit

For the moment only simple eunit tests are supported

Note: It's still a spike :-)


Cheers,
Charpi

Re: Move to GitHub, release candidate

Fabrice Nourisson — 2010-12-06T17:33:54


Le 06/12/10 18:02, Dominic Williams a écrit :
Yes, I got this failure once.
I have this error when I use extermeforge interactively, and I modify 
erl file.

Re: Move to GitHub, release candidate

Dominic Williams — 2010-12-06T17:02:05

Hi,

Le 6 déc. 2010 à 17:51, Fabrice Nourisson a écrit :


Thanks.


OK.


Do you mean that you got this failure once, but not every time?


Yes, in a sense that is normal. These are processes crashing because a test makes them crash on purpose. So you get a crash report, but the tests pass. You don't get this when you run the ./install script because that script redirects the error reporting of the test slave to a file.

I will add an explanation in the README about how to do this when you run your own Extreme Forge instance.


Thanks for the tests and feedback !

Dom
http://dominicwilliams.net

Re: Move to GitHub, release candidate

Fabrice Nourisson — 2010-12-06T16:51:41

Hi,

I check git clone, Installation and Usage.

For the Installation :
- On Ubuntu 10.04.1 LTS  - Erlang R13B03 (erts-5.7.4) : There is no failure.
- On MacOS x V 10.5.8 - Erlang R14B (erts-5.8.1). I run 3 times 
./install. I have a failure once

    Users/fafa/extermeforge/erlang-TDD/src/integrator_test.erl(21):
    failure in {integrator_test, start_stop, 0}
        Error: {badmatch,timeout}
        Stack: [{integrator_test,start_stop,0},{consul,test,3}]


For the Usage :
I do not have Erlang code, so I use ExtermeForge code to test the Usage.
I have the following trace back, when I change erl files.

    Compiling: .
    16/16 successfully compiled.
    Testing 43: ......(extremeforge< at >edgard)2>
    =ERROR REPORT==== 6-Dec-2010::17:32:41 ===
    Error in process <0.369.0> on node
    'extremeforge_extremeforge_slave< at >edgard' with exit value:
    {{nocatch,stop},[{fixtures_test,'-use_tree_destroys_tree_even_if_killed_by_parent_link/0-fun-2-',1}]}

    ...(extremeforge< at >edgard)2>
    =ERROR REPORT==== 6-Dec-2

Move to GitHub, release candidate

Dominic Williams — 2010-12-02T15:41:04

Hi,

I've moved the Extreme Forge code GitHub:

http://github.com/extremeforge

Could you check things (especially, that ./install works without any warnings or erros on your machine and your version of Erlang, read the new README, and try out the new version) before I make a new release and announce the move to GitHub?

Could someone with a Windows box try the modified install.bat and generally test things on Windows? It hasn't been done for ages...

Thanks,

Dom
http://dominicwilliams.net