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

Introduce Dropwizard Metrics integration test #1426

Merged
merged 66 commits into from
Nov 28, 2024

Conversation

rickie
Copy link
Member

@rickie rickie commented Nov 18, 2024

Credits to @oxkitsune for the initial work on this integration test!

A continuation of: #894.

Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link
Member

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pushed more changes; getting closer.

Comment on lines +78 to +79
+ <arg>-Xmaxwarns</arg>
+ <arg>1000000</arg>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added this for consistency with the Checkstyle setup. The fact that right now it doesn't have impact is a function of our checks and the code under test.

(The alternative is to drop -Xmaxwarns from both integration tests. This reduces patch maintenance at the cost of a potentially incomplete list of warnings. I guess it's fine to consistently apply the flag, for now.)

"${patch_error_prone_flags}" \
"${validation_error_prone_flags}" \
"${validation_build_flags}" \
${@}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On Mac this gives an:

$ ./integration-tests/metrics.sh 
./integration-tests/metrics.sh: line 26: @: unbound variable

If I drop the {} it works 🤔.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then let's drop it. (Also for Checkstyle.) Weird stuff :)

@rickie
Copy link
Member Author

rickie commented Nov 26, 2024

I pushed a few things that also impact the expected warnings, with which JDK version did you build exactly? I feel I'm introducing more now 🤔.

Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link
Member

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I pushed a few things that also impact the expected warnings, with which JDK version did you build exactly? I feel I'm introducing more now 🤔.

Not just more, also a few less. Very weird; can't explain yet. (But the new behavior is consistent; also observe this locally and on GitHub Actions.)

Added two more commits. @mohamedsamehsalah this PR is ready for your review 😄

Only open point is to revert some .github/workflows/run-integration-tests.yml changes. Will do if the tests pass.

Comment on lines 90 to 98
@@ -350,7 +383,7 @@
<artifactId>maven-javadoc-plugin</artifactId>
<version>3.10.1</version>
<configuration>
- <source>8</source>
+ <source>11</source>
<doclint>none</doclint>
<quiet>true</quiet>
<notimestamp>true</notimestamp>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can omit this, as we don't run Javadoc during the integration test.

Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link
Contributor

@mohamedsamehsalah mohamedsamehsalah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@rickie
Copy link
Member Author

rickie commented Nov 28, 2024

Thanks @mohamedsamehsalah !

Only open point is to revert some .github/workflows/run-integration-tests.yml changes. Will do if the tests pass.

Did this 😄.

Will run the tests once more to see if everything is good to go!

@rickie
Copy link
Member Author

rickie commented Nov 28, 2024

/integration-test

Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link
Member

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added one more commit. Suggested commit message:

Introduce Dropwizard Metrics integration test (#1426)

@Stephan202 Stephan202 changed the title Introduce Metrics integration test Introduce Dropwizard Metrics integration test Nov 28, 2024
@Stephan202 Stephan202 merged commit b3d391c into master Nov 28, 2024
16 checks passed
@Stephan202 Stephan202 deleted the rossendrijver/metrics_integration_test branch November 28, 2024 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore A task not related to code (build, formatting, process, ...)
Development

Successfully merging this pull request may close these issues.

4 participants