-
Notifications
You must be signed in to change notification settings - Fork 905
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
Add smoke test for the OTel Spring starter #8965
Add smoke test for the OTel Spring starter #8965
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice 👍
@@ -132,6 +132,8 @@ hideFromDependabot(":smoke-tests:images:servlet:servlet-3.0") | |||
hideFromDependabot(":smoke-tests:images:servlet:servlet-5.0") | |||
hideFromDependabot(":smoke-tests:images:spring-boot") | |||
|
|||
include(":smoke-tests-otel-starter") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want dependabot to update e.g. h2 or dbcp2 versions?
include(":smoke-tests-otel-starter") | |
hideFromDependabot(":smoke-tests-otel-starter") |
Also, WDYT about using e.g.
include(":smoke-tests-otel-starter") | |
include(":smoke-tests:spring-starter-smoke-test") |
? I'm trying to avoid exploding the number of directories in the root repo dir, we could put all smoke tests projects into smoke-test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hideFromDependabot
is commited.
The smoke-tests
folder contains a lot of code related to the agent smoke tests. I would suggest a clear separation between the agent smoke test code and the Spring starter smoke test code.
Perhaps after this PR, a refactoring could add agent-smoke-tests
and spring-starter-smoke-tests
subfolders into the smoke-tests
folder to:
- Separate the two smoke test codes (agent smoke test and Spring starter smoke test)
- Make the namings explicit (agent smoke test and Spring starter smoke test)
- Limit the number of second-level folders
...-tests-otel-starter/src/test/java/io/opentelemetry/smoketest/OtelSpringStarterSmokeTest.java
Outdated
Show resolved
Hide resolved
...-tests-otel-starter/src/test/java/io/opentelemetry/smoketest/OtelSpringStarterSmokeTest.java
Show resolved
Hide resolved
...-tests-otel-starter/src/test/java/io/opentelemetry/smoketest/OtelSpringStarterSmokeTest.java
Outdated
Show resolved
Hide resolved
Co-authored-by: Mateusz Rzeszutek <[email protected]>
Co-authored-by: Mateusz Rzeszutek <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
...r/src/main/java/io/opentelemetry/spring/smoketest/OtelSpringStarterSmokeTestApplication.java
Outdated
Show resolved
Hide resolved
smoke-tests-otel-starter/src/main/java/io/opentelemetry/spring/smoketest/SqlExecutor.java
Outdated
Show resolved
Hide resolved
...-tests-otel-starter/src/test/java/io/opentelemetry/smoketest/OtelSpringStarterSmokeTest.java
Outdated
Show resolved
Hide resolved
Co-authored-by: Trask Stalnaker <[email protected]>
…/smoketest/SqlExecutor.java Co-authored-by: Trask Stalnaker <[email protected]>
This PR adds a smoke test for the OTel Spring starter with library instrumentations, as discussed in #8776 and during Java SIG.
The test checks the presence of an HTTP span, an SQL span, a Logback log record, and a histogram metric.
The smoke test can be executed in a JVM or as a GraalVM native test. It will be part of the daily native test executions.