opentelemetry-java-instrume.../smoke-tests
Tyler Benson c58d259459 Make Retrys consistent (DataDog/dd-trace-java#1442) 2020-05-26 11:54:55 -07:00
..
cli Update a few last things to otel-java 0.4.0 (#399) 2020-05-11 22:17:16 -07:00
java9-modules Use java 11 for compilation (#390) 2020-05-14 15:13:30 -07:00
play Remove copyright year from license header (#322) 2020-04-15 11:24:44 -07:00
springboot Remove copyright year from license header (#322) 2020-04-15 11:24:44 -07:00
src/main/groovy/io/opentelemetry/smoketest Used BatchSpansProcessor instead of SimpleSpansProcessor (#393) 2020-05-16 13:18:43 -07:00
wildfly Make Retrys consistent (DataDog/dd-trace-java#1442) 2020-05-26 11:54:55 -07:00
README.md Rename package to io.opentelemetry.auto (#54) 2020-01-14 13:57:01 -08:00
smoke-tests.gradle A few exporter improvements (#288) 2020-03-29 08:13:20 -07:00

README.md

Smoke Tests

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

Each subproject underneath 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.