open-telemetry
/
opentelemetry-java-instrumentation
mirror of https://github.com/open-telemetry/opentelemetry-java-instrumentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
opentelemetry-java-instrume.../dd-smoke-tests
History
Nikolay Martynov 309f9e2ddb Introduce to API key config option 
To stream line configuration in the future intropduce
`DD_API_KEY`/`DD_API_KEY_FILE` to provide agent with API
key. Currently this is only used for profiling but later may be used
for other parts of the agent too.
 		2020-04-06 12:02:51 -04:00
..
cli Upgradle to gradle 6.0 2019-11-12 16:26:46 -05:00
java9-modules Format 2019-10-24 21:05:01 -07:00
play Refactor smoketests setup 2019-06-07 22:56:28 -04:00
profiling-integration-tests Introduce to API key config option 2020-04-06 12:02:51 -04:00
springboot Return TypePool.Resolution that caches 2020-02-26 12:47:48 -08:00
src/main/groovy/datadog/smoketest Introduce to API key config option 2020-04-06 12:02:51 -04:00
wildfly Attempt to improve test reliability 2020-03-04 19:02:41 -08:00
README.md Cli Application smoke test 2019-07-18 11:14:59 -04:00
dd-smoke-tests.gradle Format 2019-10-24 21:05:01 -07:00

README.md

Datadog Smoke Tests

Assert that various applications will start up with the Datadog JavaAgent without any obvious ill effects.

Each subproject underneath dd-smoke-tests is a single smoke test. Each test does the following

  • Launch the application with stdout and stderr logged to $buildDir/reports/server.log
  • For web servers, run a spock test which does 200 requests to an endpoint on the server and asserts on an expected response.

Note that there is nothing special about doing 200 requests. 200 is simply an arbitrarily large number to exercise the server.