-
Notifications
You must be signed in to change notification settings - Fork 318
Instrumentation Test Framework #177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
d11a8de to
d41897e
Compare
BytebuddyAgent install already handles class retransformation, make the custom classloader redundant.
28d8e05 to
1a80e44
Compare
| * in an initialized state. | ||
| * </ul> | ||
| */ | ||
| @SpecMetadata(filename = "AgentTestRunner.java", line = 0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just out of curiosity... what does this line do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Spock expects subclasses of spock.lang.Specification to have this annotation; adding it allows us to extend Specification from a java class.
tylerbenson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
toolingto allow the core agent and the test framework to share the same codepath for configuring the bytebuddy agent.This allows us to test instrumentation entirely in the ide/spock (no -javaagent flag required).
There are still some tests in the
dd-java-agent-ittestsproject which should be moved into their integration subproject and converted to the new test framework. These will eventually be moved over, but they're not a super high priority at the moment.