* Run tests with JUnit platform * Matcher * Restore * Don't mix JUnit4 with JUunit5 in spring tests * Separate out tests that need custom class loader. * Separate out test for a couple classes that need it, try to remove SpockRunner, but Grizzly? * Remove SpockRunner * Fix grizzly * Remove assumeTrue workaround. * Comments |
||
---|---|---|
.. | ||
reactor-3.1 | ||
servlet | ||
spring | ||
README.md |
README.md
Instrumentation Core
These modules for the core logic for library instrumentation. instrumentation should add core logic here which can be set up manually by a user, and agent-specific code for automatically setting up the instrumentation in that folder.
Note, we are currently working on separating instrumentatin projects so that their core parts can be accessed by users not using the agent. Due to the current Gradle setup, we have these two top-level folders, instrumentation and instrumentation-core, but eventually we want to move to flattening them into something like
instrumentation/
aws-sdk-2.2/
aws-sdk-2.2/
aws-sdk-2.2-auto/