-
Notifications
You must be signed in to change notification settings - Fork 192
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
Add integration tests for tracing compliance #662
Add integration tests for tracing compliance #662
Conversation
Codecov Report
@@ Coverage Diff @@
## main #662 +/- ##
============================================
- Coverage 84.45% 84.28% -0.17%
- Complexity 1141 1153 +12
============================================
Files 127 128 +1
Lines 2766 2788 +22
============================================
+ Hits 2336 2350 +14
- Misses 430 438 +8
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
any tests which are verifying behaviour from the spec compliance matrix need a group annotation, please |
Modified the names of the tests to be more descriptive and added the `@group compliance` notation. Additionally, I commented out one of the tests that I was not totally sure of. (unsure if `setAttribute()` should work with empty string `''` values.
Removed `$span->end()` calls as they shouldn't be necessary
Test to get default tracer. Also, added `@group` php unit annotation for tests to check specification compliance
@yuktea |
Some additional tests for the Span Builder SDK that verify:
startSpan()
should not workplus some additional tests for setting null and empty string values to attributes.
UPDATE: I commented out one of the tests that I was not totally sure of.
(unsure if
setAttribute()
should work with empty string''
values.)