-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Use subtests in the trace package #2594
Conversation
As this only changes tests, it shouldn't need a changelog entry. |
@@ -26,74 +26,91 @@ import ( | |||
// Taken from the W3C tests: | |||
// https://github.com/w3c/trace-context/blob/dcd3ad9b7d6ac36f70ff3739874b73c11b0302a1/test/test_data.json | |||
var testcases = []struct { | |||
name string |
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.
Technically, we could use in
as the name of the subtest here. I've added an explicit name though, as I believe it makes it clearer what the case's goal is.
Codecov Report
@@ Coverage Diff @@
## main #2594 +/- ##
=======================================
- Coverage 76.2% 76.1% -0.1%
=======================================
Files 173 173
Lines 12238 12238
=======================================
- Hits 9328 9322 -6
- Misses 2667 2673 +6
Partials 243 243
|
This is a test-only change with several approvals already; merging prior to 24h. |
As I was looking at tests within the trace package, I noticed they use range test cases, but without sub tests, making it harder to run a single test.