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.../smoke-tests
History
Trask Stalnaker 794ccd0e6b
Rename java agent artifact (#137) 
* Fix config to not rely on module alpha order

* Rename java-agent module to opentelemetry-auto
 		2020-02-06 16:03:24 -08:00
..
cli Remove trace-api artifact (#116) 2020-02-01 13:07:51 -08:00
java9-modules Rename package to io.opentelemetry.auto (#54) 2020-01-14 13:57:01 -08:00
play Remove trace-api artifact (#116) 2020-02-01 13:07:51 -08:00
springboot Simplify directory/module structure (#77) 2020-01-22 13:55:47 -08:00
src/main/groovy/io/opentelemetry/smoketest Rename package to io.opentelemetry.auto (#54) 2020-01-14 13:57:01 -08:00
wildfly Rename package to io.opentelemetry.auto (#54) 2020-01-14 13:57:01 -08:00
README.md Rename package to io.opentelemetry.auto (#54) 2020-01-14 13:57:01 -08:00
smoke-tests.gradle Rename java agent artifact (#137) 2020-02-06 16:03:24 -08: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.