Allow to use a custom application.properties per test scenario #281
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
run tests |
pjgg
suggested changes
Sep 28, 2021
...src/main/java/io/quarkus/test/services/quarkus/QuarkusApplicationManagedResourceBuilder.java
Show resolved
Hide resolved
...src/main/java/io/quarkus/test/services/quarkus/QuarkusApplicationManagedResourceBuilder.java
Show resolved
Hide resolved
...src/main/java/io/quarkus/test/services/quarkus/QuarkusApplicationManagedResourceBuilder.java
Show resolved
Hide resolved
By default, the test framework will use the `application.properties` file at `src/main/resources` folder. The service interface provides multiple methods to add properties at test scope only:
- `service.withProperties(path)`
- `service.withProperty(key, value)`
If you want to use a different application properties file for all the tests, you can add the `application.properties` file at `src/test/resources` and the test framework will use this instead.
Moreover, if you want to select a concrete application properties file for a single test scenario, then you can configure your Quarkus application using:
```java
@QuarkusScenario
public class PingPongResourceIT {
@QuarkusApplication(properties = "my-custom-properties.properties")
static final RestService pingpong = new RestService();
}
```
This option is available also for Dev Mode, Remote Dev mode and remote git applications, and works for JVM, Native, OpenShift and Kubernetes.
| Note that the test framework does not support the usage of YAML files yet [quarkus-qe#240](quarkus-qe#240)
Sgitario
force-pushed
the
overwrite_application_properties
branch
from
ee20f43 to
cea57d9
Compare
pjgg
approved these changes
Sep 28, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, the test framework will use the
application.propertiesfile atsrc/main/resourcesfolder. The service interface provides multiple methods to add properties in the scenario:service.withProperties(path)service.withProperty(key, value)If you want to use a different application properties file for all the tests, you can add the
application.propertiesfile atsrc/test/resourcesand the test framework will use this instead.Moreover, if you want to select a concrete application properties file for a single test scenario, then you can configure your Quarkus application using:
This option is available also for Dev Mode, Remote Dev mode and remote git applications, and works for JVM, Native, OpenShift and Kubernetes.
| Note that the test framework does not support the usage of YAML files yet #240