Fail test run if Common Test suite cannot be compiled

Question

If I have a syntax error in one of my Common Test suites, ct_run simply waits for 15 seconds and then continues. It displays this message:

{error,make_failed}

Failed to compile or locate one or more test suites
Press 'c' to continue or 'a' to abort.
Will continue in 15 seconds if no answer is given!
(c/a)

If I use -noshell, then it displays:

{error,make_failed}

...and continues anyway.

How do I make it abort if compilation fails?

Have you tried option `-abort_if_missing_suites` with `-noshell`? — Łukasz Ptaszyński, Jul 10 '15 at 14:42
Hm, seems I've misunderstood original question. So yah, both options needed. — Viacheslav Kovalev, Jul 10 '15 at 14:45

score 1 · Accepted Answer · answered Jul 10 '15 at 14:51

1

Answer is here. When ct_run encounters compilation error, it tries to ask you, whether you want to continue. continue/2 function does a dirty trick in order to determine if tests are run interactively. But you are able to cheat this function passing -noshell emulator option. In this case, continue/2 function will make decision based on -abort_if_missing_suites.

So, you need to ct_run -abort_if_missing_suites -erl_args -noshell.

answered Jul 10 '15 at 14:51

Viacheslav Kovalev

1,745
12
17

1

Note that this requires Erlang 17.0 or newer; we're still using Erlang R16B03-1 at the moment. – Roger Lipscombe Jul 10 '15 at 15:19
Oops. That's interesting. I didn't peek into elder versions code. – Viacheslav Kovalev Jul 10 '15 at 15:25
In 18.2, you no longer need the `-noshell` option to make `-abort_if_missing_suites` work (but we're still using 17.x...) – Roger Lipscombe Sep 19 '16 at 09:30
Important note (because I made this mistake): it only works if you put it _before_ `-erl_args`. – Roger Lipscombe Apr 16 '19 at 21:23

Fail test run if Common Test suite cannot be compiled

1 Answers1