EUnit test suite
glorybox.away at gmail.com
Sun Nov 28 16:45:54 EST 2010
I found that it produced weird results, cause I had old code installed into
erlang lib directory. After I removed that code from erlang lib directory
it started showing message :
*** test module not found ***
Running rebar without suite argument works always perfectly.
On Sun, Nov 28, 2010 at 11:41 PM, Dan Reverri <dan at basho.com> wrote:
> Hi Sergey,
> The install command was removed from rebar; rebar was not intended to be a
> package management solution and the install command introduced a lot of
> weird edge cases.
> I was not able to reproduce your issue locally; how are you determining
> that code is running from the erlang lib directory?
> I'm not sure if this is possible for your use case but you may want to
> consider not installing applications to your Erlang lib. Instead, create
> stand alone releases that contain all the required modules.
> Daniel Reverri
> Developer Advocate
> Basho Technologies, Inc.
> dan at basho.com
> On Sun, Nov 28, 2010 at 8:22 AM, Sergey Sinkovsky <glorybox.away at gmail.com
> > wrote:
>>> Sorry if this question was raised earlier.
>>> I try to run rebar eunit suite=module_name and seems like it uses code
>>> which have been installed in /usr/local/lib/erlang/lib/appname-vsn,
>>> while just running rebar eunit runs tests for local code.
>>> This is confusing, especially, after i am not able to find install
>>> command in current build.
>>> Btw, is there any blog which highlights changes in rebar?
>> Sergey Sinkovsky
>> rebar mailing list
>> rebar at lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rebar