opentelemetry-java-instrume.../dd-smoke-tests
Nikolay Martynov 851768d6d7 Revert to use waitFor() because java7 doesn't have better option 2019-08-15 11:17:05 -04:00
..
cli Revert to use waitFor() because java7 doesn't have better option 2019-08-15 11:17:05 -04:00
play Refactor smoketests setup 2019-06-07 22:56:28 -04:00
springboot Be more specific about java binary and home location in integration tests 2019-06-12 11:17:23 -04:00
src/main/groovy/datadog/smoketest Improve smoke test app log file naming 2019-06-21 12:08:31 -04:00
wildfly Require Java8 for play smoke tests 2019-06-12 11:51:58 -04:00
README.md Cli Application smoke test 2019-07-18 11:14:59 -04:00
dd-smoke-tests.gradle Refactor smoketests setup 2019-06-07 22:56:28 -04: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.