You can clone with
it runs and executes my tests. When I make changes to the tests (not the code to be tested),
it runs the old tests which are held in the .eunit directory.
If I perform a
and run the command
again, all is good.
Think you might be able to fix this? I don't use EUnit so there'd be some "start-up" costs for me. I think you could add some extra cleanup code around here:
I use eunit dialy and don't have any problems, also for model testing, where a full started boss instance is needed (boss_db, boss_news, ... started).
You should use ./rebar boss c=test_eunit
Please let me know if you have problem with this command (we use an adapted version of rebar-eunit code).
I think this is a rebar issue not a CB issue, going to close it now