Open jmacd opened 2 years ago
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Is your feature request related to a problem? Please describe.
It is difficult to test correctness in an OTel Collector exporter, receiver, or processor. There are some utilities for printing human-readability differences between
pdata
objects, but they are somewhat incomplete and/or under-tested themselves.Describe the solution you'd like
Would like to see improvements in testing for all components by making use of improved, shared testing utilities.
Describe alternatives you've considered
The status quo means we do less correctness testing than we'd like.
Additional context
A TODO was left in the code following https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/12951#discussion_r994879316. Currently, users of the
DiffMetrics()
utility are not correctly witnessing differences in certain parts of the metrics data point.