Skip to content
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

Provide instrumentation configuration #7

Closed
dodie opened this issue Sep 11, 2016 · 1 comment
Closed

Provide instrumentation configuration #7

dodie opened this issue Sep 11, 2016 · 1 comment

Comments

@dodie
Copy link
Owner

dodie commented Sep 11, 2016

Now the instrumentation happens automatically for every test class.
It would be more flexible if the user could specify the test classes or methods to be instrumented - for example with package whitelists or manually placed annotations in the test code.

I think keeping the Listener and the ability to add the Rule manually while providing an opt-out mechanism from the automatic instrumentation would provide flexibility for the users, in case of somebody prefers to manually select test classes for augmentation.

@dodie
Copy link
Owner Author

dodie commented Sep 17, 2016

By default, Scott instruments methods with org.junit.Test annotations, and injects the ScottRule to every class that have at least one method with the org.junit.Test annotation.

This behaviour can be overridden with scott.track.method_annotation and the scott.injectrule.method_annotation JVM arguments.

@dodie dodie closed this as completed Sep 17, 2016
@dodie dodie modified the milestone: 2.0 Oct 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant