opentelemetry-java-instrume.../smoke-tests
Nikita Salnikov-Tarnovski 6e1c0436da
Clarifications about various test tasks (#358)
In addition this commit replaces eager tasks generation for running tests using different java versions with rule based task created on-demand.
2020-04-28 18:11:17 -07:00
..
cli Remove copyright year from license header (#322) 2020-04-15 11:24:44 -07:00
java9-modules Clarifications about various test tasks (#358) 2020-04-28 18:11:17 -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 Remove copyright year from license header (#322) 2020-04-15 11:24:44 -07:00
wildfly Remove copyright year from license header (#322) 2020-04-15 11:24:44 -07:00
README.md
smoke-tests.gradle

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.