Cover entire pages with bUnit

[SviatoslavK]

I stumbled upon the weird problem with bUnit and am unsure if it is a bug or my misuse of bUnit. I'm doing a small integration test on a page. It looks something like this:

• Find the button for adding a note on the page, click, make sure that a note appears on the page
• Click on this note, and a sidebar should appear to edit it
• Change note in the sidebar
• Delete selected note
  For asynchronous actions, I use WaitForAssertion. And the problem is that the tests are written correctly, but they periodically crash without waiting for a timeout or not finding elements on the page. Perhaps this is because the rendering order of the components is different for different test runs? Or I won't be able to cover entire pages with tests using your library?

Version info:

• bUnit version: 1.1.5
• .NET 5, Blazor Server

[egil]

Hi @SviatoslavK

In general, a page in Blazor is just a component, so bUnit has no problem with that. What you are experiencing can be any number of things, so without a sample that reproduces the issue I cannot really help.

Ill convert this to a discussion. If you have any additional info, please share it, and ill be happy to help more if I can.

[SviatoslavK]

Thank you for looking up to my issue. It is not easy to distill the problem I have into something reproducible. May I ask you for any suggestions for bUnit debugging techniques that I may use to get there?

[egil]

You can just set breakpoints in the code and figure out what's going on.

You can also add a logger to bunit to get some insights into the renderer and what's going on, see https://bunit.dev/docs/misc-test-tips.html#capturing-logs-from-ilogger-in-test-output

[SviatoslavK]

Thanks a lot for your advices!