Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amend QUARKUS-2812 test plan #145

Merged
merged 1 commit into from
Jul 10, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 11 additions & 0 deletions QUARKUS-2812.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,12 @@ Build failure prevents the metrics to be processed.
Failure in the metrics collection (i.e. a bug in Quarkus) causes the build to fail.
Failure in the metrics sendoff (network issue, endpoint unavailability, ...) does NOT cause the build to fail.

Metrics are off by default. During the first run of an application in dev mode, a prompt is displayed, which allows user
to activate the feature. There are 3 defined actions:
- Enable.
- Disable.
- No action - the prompt times out after 10 seconds and will be displayed again during next dev mode run.

## Scope of testing

What data is collected in what event.
Expand All @@ -40,6 +46,8 @@ Verify the data being logged during application build.

Verify, that no sensitive data / personal identifiable information is being shared (e.g. IP address).

Verify the prompt to enable the metrics in the dev mode. Verify that the feature is opt-in.

Verify all the mechanisms to disable the metrics work properly.
- Quarkus config property.
- Static list of group IDs.
Expand Down Expand Up @@ -84,3 +92,6 @@ Number of new scenarios:
- ~1 minute of build time each
- 2 in native mode: extensionsSetA (small), extensionsSetB (large).
- ~5 minutes of build time each.

By default, the prompt in dev mode should be disabled in all dev-mode tests in all test suites via the Quarkus config
property.