Describe the bug
As I wanted to separate native and "normal" tests, I made two TestProfiles, each of them have a custom TestResource with a MariaDB container (using testcontainers) on them. Each MariaDB has their own schema name etc (I changed it as I've seen native tests are using the same schema and container as normal tests) .
First issue came when I tried to set jdbc parameters for native tests in their own TestResource, it doesn't work.
Second issue, when setting them manually in "application.properties", it doesn't connect.
So, it looks like TestResources doesn't work on native tests. MariaDB container for native tests isn't used or started.
Expected behavior
Custom parameters set in TestResource for native tests are applied.
Custom TestResource for native tests are started and used.
Actual behavior
Neither parameters nor container is started in native tests.
Describe the bug As I wanted to separate native and "normal" tests, I made two TestProfiles, each of them have a custom TestResource with a MariaDB container (using testcontainers) on them. Each MariaDB has their own schema name etc (I changed it as I've seen native tests are using the same schema and container as normal tests) .
First issue came when I tried to set jdbc parameters for native tests in their own TestResource, it doesn't work. Second issue, when setting them manually in "application.properties", it doesn't connect.
So, it looks like TestResources doesn't work on native tests. MariaDB container for native tests isn't used or started.
Expected behavior
Custom parameters set in TestResource for native tests are applied. Custom TestResource for native tests are started and used.
Actual behavior
Neither parameters nor container is started in native tests.
To Reproduce Steps to reproduce the behavior:
Unzip attached reproducer quarkus_issue.zip
Execute ./mvnw clean verify -Dnative
Look native tests failing as it can't connect to native test resource, which is a testcontainer's Maria DB.
Configuration
Screenshots (If applicable, add screenshots to help explain your problem.)
Environment (please complete the following information):
uname -a
orver
: 5.4.0-42-genericjava -version
: openjdk version "11.0.8" 2020-07-14mvnw --version
orgradlew --version
): Apache Maven 3.6.3Additional context I changed profile for generated native build, as I didn't want it to be default "prod".
https://github.com/quarkusio/quarkus/issues/11146
$upstream:11146$