Using Telemetry to improve testing

Eventide’s Telemetry library enables you to separate what happened from what you want to do about it. This has an obvious use as a graceful way to log system behavior.

But the uses of it go beyond that. Can we turn the data we collect with Telemetry to aid in our testing?

We sure can, and in fact, that’s how the `Messaging::Write` substitute works.

So the plan is to develop something like `Messaging::Write`, complete with a substitute, and show how we can leverage Telemetry to give us the visibility we need to successfully test that the code is doing what we think it does.

And as part of it, we’ll go through how `Messaging::Write` and its substitute work, gaining a better understanding of the methods that the substitute provides when writing tests.

Join us on Zoom: https://aumni-fund.zoom.us/j/83094973603?pwd=RGp6a0hwS2twc0tJN01OVHEza2Ivdz09

To join us on Zoom though, you'll need to RSVP to the Meetup event with the same name you'll use on Zoom.