Repository navigation
Upgrade to 2.17 Breaks C# Bunit Tests #217
|
Describe the bug or question Also, please include all exceptions encountered from the cut... all we get now is the following which is not very helpful: Example: |
Replies: 7 comments 1 reply
|
Hi @roysurles I get this is frustrating, however, I am not sure this issue belongs here. You might want to raise it with Telerik instead, since that is what has changed in your setup, right? Telerik should be able to tell you what is required by their components to be rendered with bUnit. Remember to include information such as .net version and bUnit version. As for including all exceptions from the CUT, please create an issue with a example of a component that throws when rendered with bUnit, and what exceptions you expect to see. Otherwise it is hard for me to reproduce the problem. |
|
@roysurles Can you please include the complete test method so we can identify any issues or API calls that need to be made? |
Please let me know if you need additional info.. thank you! |
@roysurles always include .net version and bUnit version when bug reporting (already included Telerik version). |
|
PS C:\Users\rsurles> dotnet --info Runtime Environment: Host (useful for support): .NET Core SDKs installed: .NET Core runtimes installed: To install additional .NET Core runtimes or SDKs: Ticket details |
|
Thanks @roysurles Let me see if I can find someone to help with this. |
|
Hi everybody, |
Hi everybody,
Here is a link to the Telerik Blazor feedback portal about the issue: Upgrade to 2.17 Breaks C# Bunit Tests. The problem is already fixed and will be available with the release 2.18.0 expected near the end of October.