Documentation for quarkus.test.profile not mentioning multi-profile support?

[marcelstoer]

Describe the bug

https://quarkus.io/guides/continuous-testing#configuring-continuous-testing currently documents quarkus.test.profile as not having multi-profile support.

The profile (dev, test or prod) to use ...

Type: string

Since Quarkus now accepts quarkus.profile to be a comma-separated list of profiles, I expected the same support for quarkus.test.profile. And indeed, running Quarkus using -Dquarkus.test.profile=foo,bar does seem supported.

Profiles bar,foo activated.

Yet, the documentation still lists quarkus.test.profile as being a single string.

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[marcelstoer]

Oh, same situation here for quarkus.profile: https://quarkus.io/guides/config-reference#configuration-reference.

[quarkus-bot]

/cc @MichalMaler (documentation), @ebullient (documentation), @inoxx03 (documentation), @michelle-purcell (documentation), @rolfedh (documentation), @sheilamjones (documentation), @sunayna15 (documentation)

[geoand]

Would you like to propose an improvement?

[marcelstoer]

Sure, I was just waiting for a confirmation that this indeed is a docs bug rather than a misunderstanding on my behalf 😄

[marcelstoer]

At first I was really confused how the implementation can be so inconsistent with your documentation, knowing that your reference docs is generated from code.

After some digging and grepping in your code to find the correct classes I found this

quarkus/core/deployment/src/main/java/io/quarkus/deployment/dev/testing/TestConfig.java

Line 16 in 71f3200

* TODO refactor code to actually use these values

and this

quarkus/core/runtime/src/main/java/io/quarkus/runtime/ConfigConfig.java

Lines 13 to 17 in 71f3200

	* We don't really use this, because these are configurations for the config itself, so it causes a chicken / egg
	* problem, but we need it for documentation purposes.
	* <br>
	* Relocation of the Config configurations to the Quarkus namespace is done in
	* {@link io.quarkus.runtime.configuration.ConfigUtils#configBuilder}.

It all makes sense now 🤓 It explains why I found no references to those profile() methods. This in turn confirms that I can change the types from String to List<String> without breaking anything.