Add "send a test error" step to setup instructions

[joshuap]

Our in-app onboarding workflow waits for a test error to be reported. It's ideal if you can report a test error from their dev environment, without waiting to deploy. Can the setup instructions in the README include this? It looks like the "Using the SDK manually" instructions already do, but some of the others do not.

When this is done, let me know and I can update our docs site, which is built using the README:

https://docs.honeybadger.io/lib/dotnet/

[subzero10]

Can the setup instructions in the README include this?

Sure, I'll go over them and make sure that they include guidelines to end up with a test error being reported.

Additionally, I'm planning to create a CLI tool for deployment tracking (see #16); 🤔 I could add a command to send a test error as well.

[joshuap]

Can the setup instructions in the README include this?

Sure, I'll go over them and make sure that they include guidelines to end up with a test error being reported.

Additionally, I'm planning to create a CLI tool for deployment tracking (see #16); 🤔 I could add a command to send a test error as well.

The Ruby gem includes test and install (which also calls test) commands in addition to deploy. The key for the test is that it's using the user's config. Ideally it would route the test error through a middleware stack or some other primary integration like the gem does, but that's not required. Ruby is kind of special since we can monkey patch the world. :) Most of the other clients include manual instructions, which tbh isn't great but better than nothing.

@stympy and I have also been talking about how we can add some test data for insights to the setup/onboarding process for client libraries that support it, like maybe sending a "ping" event on startup. That would especially be useful for detecting when the client library is first deployed, but we could also use it in development.

Finally, re: CLIs in general, we've also talked about replacing the client-specific CLIs with a global one. In fact, we have one started here. So you guys may want to discuss.