Closed Sziadan closed 1 year ago
Hey @Sziadan,
thanks for reporting. The change was more or less intentional, but let's find out. A bit of context: The first version (bUnit 1.12
) behaves closer to the Blazor renderer. The Blazor renderer does not escape quotes.
Now it would be interesting to know what your component under test looks like, from a csharp code point of view but also if it is rendered in the browser.
I see, after looking a bit closer at our own code I realized we must have screwed something up ourselves too as those icons didn't render anyway.
However, the buttons did get rendered and were functional in a browser, hence why we never reacted to it I suppose.
Thanks for the heads up though, removing the icons in the code made the tests work as expected.
Thanks for the heads up though, removing the icons in the code made the tests work as expected.
Sure thing. I suppose we can close the issue for now?
Yes, the issue I were having is resolved with this. Thanks for the help!
Describe the bug We recently migrated our code to .NET 7 from .NET 6 (and updated to latest version of bUnit.web) and noticed that our test that was using bUnit started to fail.
Example: The code in question looks like this:
Result: I noticed that the rendered markup looks strange for the component we're trying to find, seems like the icon is throwing it off.
Expected: The same button, but in .NET 6 using bUnit.web 1.8.15
Version info:
(Originally posted this elsewhere but later figured it's probably not related to that issue so posted it like this instead.)