rebar/inttest/ct2/ct2_rt.erl

-module(ct2_rt).

-compile(export_all).


files() ->
    [{create, "ebin/foo.app", app(foo)},
     {copy, "../../rebar", "rebar"},
     {copy, "foo.test.spec", "foo.test.spec"},
     {copy, "foo_SUITE.erl", "test/foo_SUITE.erl"}].

run(_Dir) ->
    {ok, _} = retest:sh("./rebar compile ct -vvv"),
    ok.

%%
%% Generate the contents of a simple .app file
%%
app(Name) ->
    App = {application, Name,
           [{description, atom_to_list(Name)},
            {vsn, "1"},
            {modules, []},
            {registered, []},
            {applications, [kernel, stdlib]}]},
    io_lib:format("~p.\n", [App]).
Add -spec support to rebar_ct command line This change adds support for executing ct test runs based on test specificiations, which was missing previously. The rebar_ct module now looks for any number of files with a name ending in `test.spec` and if it finds one or more, passes these after the `-spec` argument to ct_run instead of explicitly configuring the config, user config and coverage config variables. When no specifications are found, then the module behaves as it did before this change, and both the ct1 and (new) ct2 integration tests appear to show this is a backwards compatible patch. 2011-01-26 02:00:53 +00:00			`-module(ct2_rt).`

			`-compile(export_all).`


			`files() ->`
			`[{create, "ebin/foo.app", app(foo)},`
			`{copy, "../../rebar", "rebar"},`
Fix inttest/ct2 ct spec file location (Thanks Peter Andersson) The DirRef in the spec file is relative to the directory where the spec file is located. ct2_rt was erroneously copying the spec file to test/. 2012-09-03 09:39:51 +00:00			`{copy, "foo.test.spec", "foo.test.spec"},`
Add -spec support to rebar_ct command line This change adds support for executing ct test runs based on test specificiations, which was missing previously. The rebar_ct module now looks for any number of files with a name ending in `test.spec` and if it finds one or more, passes these after the `-spec` argument to ct_run instead of explicitly configuring the config, user config and coverage config variables. When no specifications are found, then the module behaves as it did before this change, and both the ct1 and (new) ct2 integration tests appear to show this is a backwards compatible patch. 2011-01-26 02:00:53 +00:00			`{copy, "foo_SUITE.erl", "test/foo_SUITE.erl"}].`

			`run(_Dir) ->`
inttest/ct2: enable rebar DEBUG log level 2012-09-03 09:40:18 +00:00			`{ok, _} = retest:sh("./rebar compile ct -vvv"),`
Add -spec support to rebar_ct command line This change adds support for executing ct test runs based on test specificiations, which was missing previously. The rebar_ct module now looks for any number of files with a name ending in `test.spec` and if it finds one or more, passes these after the `-spec` argument to ct_run instead of explicitly configuring the config, user config and coverage config variables. When no specifications are found, then the module behaves as it did before this change, and both the ct1 and (new) ct2 integration tests appear to show this is a backwards compatible patch. 2011-01-26 02:00:53 +00:00			`ok.`

			`%%`
			`%% Generate the contents of a simple .app file`
			`%%`
			`app(Name) ->`
			`App = {application, Name,`
			`[{description, atom_to_list(Name)},`
			`{vsn, "1"},`
			`{modules, []},`
			`{registered, []},`
			`{applications, [kernel, stdlib]}]},`
			`io_lib:format("~p.\n", [App]).`