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
Anuraag Agrawal 6c1dabf782
Tag smoke test images with date and run ID from workflow. (#1559) 
* Tag smoke test images with sha from workflow.

* Pass tag as date from workflow

* Echo tag which is nice to see in logs

* Add run ID

* Remove seconds

* Missed files
 		2020-11-05 19:11:29 +09:00
..
fake-backend Tag docker images for smoke tests with date and time. (#1553) 2020-11-05 00:02:33 +09:00
grpc Tag smoke test images with date and run ID from workflow. (#1559) 2020-11-05 19:11:29 +09:00
play Tag smoke test images with date and run ID from workflow. (#1559) 2020-11-05 19:11:29 +09:00
springboot Tag smoke test images with date and run ID from workflow. (#1559) 2020-11-05 19:11:29 +09:00
src/test Smoke tests using Jaeger and Zipkin exporters (#1543) 2020-11-02 20:50:14 -08:00
README.md Rename package to io.opentelemetry.auto (#54) 2020-01-14 13:57:01 -08:00
smoke-tests.gradle Remove usage of Contexts from grpc instrumentation. (#1426) 2020-10-21 09:58:45 +09: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.