opentelemetry-java-instrume.../smoke-tests
Nikita Salnikov-Tarnovski e61ff5bac2
Rename auto-exporters' artifacts names (#514)
2020-06-14 10:53:51 -07:00
..
cli Make rootDir usage consistent (DataDog/dd-trace-java#1518) 2020-06-11 10:14:02 -07:00
java9-modules Make rootDir usage consistent (DataDog/dd-trace-java#1518) 2020-06-11 10:14:02 -07:00
play Make rootDir usage consistent (DataDog/dd-trace-java#1518) 2020-06-11 10:14:02 -07:00
springboot Make rootDir usage consistent (DataDog/dd-trace-java#1518) 2020-06-11 10:14:02 -07:00
src/main/groovy/io/opentelemetry/smoketest Embed exporters into agent jar (#491) 2020-06-11 09:41:11 +03:00
wildfly Make rootDir usage consistent (DataDog/dd-trace-java#1518) 2020-06-11 10:14:02 -07:00
README.md Rename package to io.opentelemetry.auto (#54) 2020-01-14 13:57:01 -08:00
smoke-tests.gradle Rename auto-exporters' artifacts names (#514) 2020-06-14 10:53:51 -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.