How to create a release with the test dependencies?

Questions / Help
,
1

Hello!

The Erlang project I’m working on is using rebar3. There are a few dependencies like meck that are only in the test profile, because they are only supposed to be used during local testing, i.e. after rebar3 as test shell.

As far as I understand our CI pipeline, testing and production environment, during the build process a Linux image is created where the Erlang application is generated into with the rebar3 as prod release command, then this image is started by Kubernetes in the integrated test environments and I can log into the container, into the Erlang shell, etc.

However, in the integrated testing environment I’d like to use some of those applications from the test profile (e.g. I can simulate some errors with meck). However, the image in the Kubernetes environment doesn’t have meck.

I tried to create a release (so far only locally) with rebar as test prod, but this release seems to lack the applications that are only in the test profile. Is it supposed to work like this? Is there a way to include applications from the test profile into a release?

2

I think that you need to add relx entry for test profile. Release respects only applications mentioned in release entry in rebar.config. Something like:

{profiles,
    [{test,
        [{deps, [my_test_dep]},
        {relx,
            [{release, {my_test_release, "0.1.0"},
                [{my_app, "0.1.0"},
                 {my_test_dep, "0.1.0"}]}
            ]}
        ]}
    ]
}.
2 Likes
3

Thanks, it seems to work (at least the generated release does have the debug applications).