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
How to Unit Test SignalR #11052
Comments
I wrote lib (available via nuget) which provide support for unit testing in signalR core (both There are examples in docs too. |
Yes, this would be very helpful for developers not only for testing, but also do understand better SignalR through unit tests. |
Adding my +1 as unit testing documentation would be extremely helpful. |
Yes especially te proper way to mock Hubs and Clients would be super usefull. |
+1 |
+1 |
1 similar comment
+1 |
+1 |
2 similar comments
+1 |
+1 |
Any update Code Maintainers? |
We would find this very useful as well |
yes, this would be great, I was trying with old documentation. |
+1 |
yes, pl. share any documentation or sample unit test projects. Thanks. |
Any update ? |
any updates? |
Any update? Hope for the unit testing support not only for the server but also for the client |
+1 |
Doc request for unit testing signalr in a ASP.NetCore 2.2 app
I am currently working on a signalr application and I want to be able to test my hubs. I couldn't find any information about unit testing signalr in AspNetCore/SignalR. The only information that i could find was from 2013 for AspNet/SignalR and is pretty outdated.
I am sugesting to put the topic about unit testing signalr on this location:
Docs/ASP.NET/ASP.NET Core/ASP.NET Core 2.2/Real-time apps/Unit testing
or
Docs/ASP.NET/ASP.NET Core/ASP.NET Core 2.2/Test, debug and roubleshoot/Unit testing/signalr hubs
This topic will cover the following topics:
Testing of hubs, testing of groups and examples.
A rough outline:
-- Using MSTest
-- Using NUnit
-- Using xUnit
-- Using MSTest
-- Using NUnit
-- Using xUnit
I hope this gets added because there is not a lot of information on this topic.
The text was updated successfully, but these errors were encountered: