The test output is missing in the console

[ppalaga]

The output of a Camel Quarkus integration test is missing in the console.

Steps to reproduce:

git clone https://github.com/apache/camel-quarkus.git
cd camel-quarkus
mvnd clean install -DskipTests
cd integration-tests/base64
mvnd clean test

The actual output is

[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO] 

Note that there is no output of the booting app and no output of the test. I'd expect the output to be much like with plain mvn:

mvn clean test
...
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.camel.quarkus.component.base64.it.Base64Test
2020-02-25 08:35:05,077 INFO  [org.apa.cam.qua.cor.FastCamelContext] (main) Apache Camel 3.0.1 (CamelContext: camel-1) is starting
2020-02-25 08:35:05,078 INFO  [org.apa.cam.imp.eng.DefaultManagementStrategy] (main) JMX is disabled
2020-02-25 08:35:05,118 INFO  [org.apa.cam.qua.cor.FastCamelContext] (main) StreamCaching is not in use. If using streams then its recommended to enable stream caching. See more details at http://camel.apache.org/stream-caching.html
2020-02-25 08:35:05,121 INFO  [org.apa.cam.qua.cor.FastCamelContext] (main) Route: route1 started and consuming from: direct://start
2020-02-25 08:35:05,124 INFO  [org.apa.cam.qua.cor.FastCamelContext] (main) Total 1 routes, of which 1 are started
2020-02-25 08:35:05,125 INFO  [org.apa.cam.qua.cor.FastCamelContext] (main) Apache Camel 3.0.1 (CamelContext: camel-1) started in 0.048 seconds
2020-02-25 08:35:05,127 INFO  [io.quarkus] (main) Quarkus 1.3.0.Alpha2 started in 1.466s. Listening on: http://0.0.0.0:35711
2020-02-25 08:35:05,128 INFO  [io.quarkus] (main) Profile test activated. 
2020-02-25 08:35:05,128 INFO  [io.quarkus] (main) Installed features: [camel-base64, camel-core, camel-direct, camel-policy, camel-support-common, cdi, resteasy]
2020-02-25 08:35:06,019 INFO  [org.apa.cam.qua.com.bas.it.Base64Resource] (executor-thread-1) Sending to base64: Hello World
2020-02-25 08:35:06,036 INFO  [org.apa.cam.qua.com.bas.it.Base64Resource] (executor-thread-1) Got response from base64: SGVsbG8gV29ybGQ

[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.734 s - in org.apache.camel.quarkus.component.base64.it.Base64Test
2020-02-25 08:35:06,122 INFO  [org.apa.cam.qua.cor.FastCamelContext] (main) Apache Camel 3.0.1 (CamelContext: camel-1) is shutting down
2020-02-25 08:35:06,126 INFO  [org.apa.cam.mai.MainLifecycleStrategy] (main) CamelContext: camel-1 has been shutdown, triggering shutdown of the JVM.
2020-02-25 08:35:06,129 INFO  [org.apa.cam.qua.cor.FastCamelContext] (main) Apache Camel 3.0.1 (CamelContext: camel-1) uptime 1.052 seconds
2020-02-25 08:35:06,129 INFO  [org.apa.cam.qua.cor.FastCamelContext] (main) Apache Camel 3.0.1 (CamelContext: camel-1) is shutdown in 0.007 seconds
2020-02-25 08:35:06,166 INFO  [io.quarkus] (main) Quarkus stopped in 0.044s
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO] 

Checking target/surefire-reports seems to suggest that the test was run, so this is probably just the matter of the missing output.

[ppalaga]

Checking target/surefire-reports seems to suggest that the test was run, so this is probably just the matter of the missing output.

Indeed, when I add Assertions.fail(); to the test, the build fails as expected.

[gnodet]

I'll try to have a look, I've seen this behavior too.

[ppalaga]

Fixed via #105