[erlang-questions] rebar and compiling common test suites

Tim Watson watson.timothy@REDACTED
Fri Jul 29 19:58:49 CEST 2011

The way rebar's common_test support works, it takes advantage of the
fact that common_test automatically compiles test suites (and helper
modules) for you. So the rebar compiler isn't normally used for ct
support. I'm assuming that you're setting src_dirs to include "test"
because you want to compile them *manually* for some reason - is this
essential? I might be able to suggest where to dig around in the rebar
code to figure out why these modules are being excluded from compile
(despite the "test" dir being included in src_dirs) but I don't fancy
digging around if you're just unaware that `rebar ct` "just works" -
let me know eh.



On 29 July 2011 17:12, Joel Reymont <joelr1@REDACTED> wrote:
> I have common test suites under test/ and have added {src_dirs, ["test"]} to rebar.config.
> Still, Erlang code under test/ is not compiled when I run 'rebar compile'.
> Is there a way to fix this?
>        Thanks, Joel
> --------------------------------------------------------------------------
> - for hire: mac osx device driver ninja, kernel extensions and usb drivers
> ---------------------+------------+---------------------------------------
> http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont
> ---------------------+------------+---------------------------------------
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

More information about the erlang-questions mailing list