Live test coverage for diagnostics and logging

[jsquire]

Summary

The Event Hubs client has a rich set of logging and diagnostics information that it makes available, exposing via ETW events and the System.Activities constructs. Though the current implementation for track two is relying on an internal track one client, that client is producing the diagnostics information, which will be ported to the new API in the near future.

Scope of Work

• Using the set of diagnostics tests for the track one client as inspiration, evaluate and bring forward those which are believed to be relevant into the track two live tests.

• Ensure that the tests are marked as [NonParallelizable] due to the nature of the diagnostics namespaces and their use of shared state.

• The tests that are brought forward should continue to pass reliably based on the telemetry emitted from the internal track one client.

Out of Scope

• Changes to any references within the TrackOneClient code; that will remain as-is.

• Moving the telemetry from the internal track one client to the track two types; that will be covered under a dedicated workstream.

Success Criteria

• The diagnostics and logging information expected to be relevant to the track two implementation is covered under a set of Live tests that have a close parity with those form the track one suite.

• The tests continue to pass reliably, both locally and within the engineering system.