Skip to content

Tracer tests #21

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

Merged
merged 3 commits into from
Aug 12, 2020
Merged

Tracer tests #21

merged 3 commits into from
Aug 12, 2020

Conversation

pankajagrawal16
Copy link
Contributor

Issue #, if available:

Description of changes:

Test coverage for Tracer functionality.

image

Checklist

Breaking change checklist

RFC issue #:

  • Migration process documented
  • Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

withEntitySubsegment(SERVICE_NAME, name, entity, subsegment);
}

public static void withEntitySubsegment(String namespace, String name, Entity entity, Consumer<Subsegment> subsegment) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some overloaded method for letting users to pass namespace as well if needed, else it will pic the default from service name

@@ -58,15 +58,6 @@ public Object around(ProceedingJoinPoint pjp,
}
}

private Object response(ProceedingJoinPoint pjp, Object methodReturn) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed this for now unless we really need to.

@stevehouel
Copy link
Contributor

Could you just add a bit of documentation just to explain for what purpose this class has been designed. I did not ask for a fully documented javadoc things, but just one sentence. Otherwise good job, it's good to start for that quality of test.

@stevehouel stevehouel self-requested a review August 12, 2020 06:56
Copy link
Contributor

@stevehouel stevehouel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I said on a previous comment. Only one or two line of documentation for each class otherwise good job.

@pankajagrawal16
Copy link
Contributor Author

Could you just add a bit of documentation just to explain for what purpose this class has been designed. I did not ask for a fully documented javadoc things, but just one sentence. Otherwise good job, it's good to start for that quality of test.

I can take that as a separate PR to quickly document the intent of each of such classes.

@stevehouel
Copy link
Contributor

Could you just add a bit of documentation just to explain for what purpose this class has been designed. I did not ask for a fully documented javadoc things, but just one sentence. Otherwise good job, it's good to start for that quality of test.

I can take that as a separate PR to quickly document the intent of each of such classes.

Ok perfect.

@stevehouel stevehouel self-requested a review August 12, 2020 07:18
@stevehouel stevehouel merged commit 95393ab into master Aug 12, 2020
@stevehouel stevehouel deleted the tracer-tests branch August 12, 2020 07:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants