-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing code using EventProcessorHost #433
Comments
For example, it would be nice if at least we could create EventData objects with user defined SystemProperties in an easy way. |
We are aware of the issue. Getting proper mocking in place would make our own testing easier and better, too. The problem is that it's a big work item with only indirect benefits, so it's hard to get on the schedule. Regarding the specific request to make EventData completely creatable, that is a small enough change that I can probably sneak it into the next release. |
Awesome, thank you! |
@fredxfred See PR #435 -- we already made this change in some of our other SDKs so there should be no issue getting it in here. |
EventData change released in 2.3.0. |
I would like to vote for this as well. Are there any updates on providing a local/embedded event hub we could use for integration testing? |
This client is now legacy and deprecated. We will still be making fixes for issues that impact customers in production but we won't be investing in new feature work. The new Java client is at https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/eventhubs/azure-messaging-eventhubs -- opening an issue there with the "Event Hubs" tag will get the attention of the right people. |
Thank you @JamesBirdsall! I will open one there. |
Actual Behavior
Expected Behavior
It would be really nice to be able to be able to somehow locally emulate an eventhub so that I can test my code using Azure EventHubs locally. Currently, the only way I can fathom to run tests (short of trying to reverse engineer backend logic) is to provision special test resources and write separate code to handle populating those resources with data, which is much more time consuming and complicated than it needs to be. With Kafka, you can create a "cluster" locally, which is very convenient compared to the testing story with Event Hubs.
The text was updated successfully, but these errors were encountered: