Description
Feature Request
Motivation
I'm writing a 3rd party library for instrumenting programs with tracing spans https://github.com/yaahc/spandoc that I would like to be able to test using the tracing test framework without having to vendor the test framework or write my own test subscriber.
Proposal
Publish the contents of tracing/tracing/tests/support
and any other necessary machinery so that they can be added as a dev dependency to spandoc
and tests can be created that verify span entry and exit ordering.
It is not necessary for the tracing crates themselves to depend on the published version via crates.io. Eliza has some worries about introducing a need to maintain API stability into the test framework, not depending on the published version should make this a less important concern, its okay if the published version drifts from the actively used version by the main tracing
crates so long as the core functionality that is published to crates.io still works.
Alternatives
Alternatively I can just vendor support files into my crate and depend on them in the same way that tracing crates do.