Skip to content
Permalink

Comparing changes

This is a direct comparison between two commits made in this repository or its related repositories. View the default comparison for this range or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: quarkus-qe/quarkus-test-plans
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 60f47d4f84400f94ebf721dcfe9e74c2b6e12a07
Choose a base ref
..
head repository: quarkus-qe/quarkus-test-plans
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: fa6751d2f713d4074c00e4490f26064ca986666a
Choose a head ref
Showing with 2 additions and 2 deletions.
  1. +2 −2 QUARKUS-3456.md
4 changes: 2 additions & 2 deletions QUARKUS-3456.md
Original file line number Diff line number Diff line change
@@ -38,12 +38,12 @@ Most importantly, the PR closed [Quarkus issue #29172](https://github.com/quarku

We test secret key handlers in the `config` module of the Quarkus QE Test Suite.

### Impact on test suites and testing automation
## Impact on test suites and testing automation
Three new integration test classes will be added to Quarkus CLI module of the Quarkus QE Test Suite.
One for each `quarkus config` subcommand (`set`, `remove`, `encrypt`).
Tests will run in a JVM mode only as intention is to test CLI and assure that `application.properties` are updated correctly.

### Impact on resources
## Impact on resources
We will start JVM application once per each test class and call an endpoint or two, therefore additional test execution time should be below 30 seconds.

## Future considerations