CUT Markup does not match IElement Markup

[rileyharris7]

I can try to recreate a runnable example, but first wanted just to describe and show what is going on - if the solution can be more simply figured out that way.

I have written a test that is verifying that a Form in the Completed state should be read only. I do that by checking that there are no form buttons displayed and that all inputs are either disabled or readonly.

For some reason my test is failing only on certain run throughs where it seems like the IElements I query are not reflecting the CUT's markup.

Do you know why this could be or if I am doing something wrong?

EDIT: This also only seems to fail when running all my test classes in one go rather than each test class individually. This makes me suspicious that something is at play similar to in #1247 with the service dependencies. If so...not really sure a great way around that.

    [Theory, AutoData]
    public void SubmittedForm_ShouldBeReadOnly(Form form)
    {
        // [Arrange]
        form.StatusID = Status.Completed;
        IFormService formService = Services.GetRequiredService<IFormService>();
        formService.Form = form;
        var cut = RenderComponent<FormComponent>();

        // [Act]
        var formButtons = cut.FindComponent<FormButtons>();
        var textBoxFormElements = cut.FindAll("span.k-textbox input, input[inputmode='decimal']");
        var allOtherFormElements = cut.FindAll("span.k-dropdownlist, span.k-textarea, span.k-combobox, input.k-checkbox, li.k-radio-item");

        // [Assert]
        Assert.Empty(formButtons.Markup);

        foreach (var element in textBoxFormElements)
        {
            Assert.True(element.HasAttribute("readonly"));
        }

        foreach(var element in allOtherFormElements)
        {
            Assert.Contains("k-disabled", element.GetAttribute("class"));
        }
    }

[linkdotnet]

Hey @rileyharris7,

some small questions for clarification:

1. On which version of bUnit are you? If it is the latest [1.25.3](https://www.nuget.org/packages/bunit/1.25.3) stable - could you checkout the preview build? (1.26.26-preview)?
2. Is there any async code going on in your component? Especially OnInitializedAsync

[rileyharris7]

Hey @linkdotnet,

1. I was on 1.22 and just updated to the latest preview that you mentioned - unfortunately the error was still occurring.
2. Yes, I do override the OnInitializedAsync method and perform some asynchronous operations there. Is there a certain way I should be handling / arranging that in my tests to prevent issues?

[linkdotnet]

Regarding 2: Yes.
I would just refer to the docs here, as they explain it quite well: https://bunit.dev/docs/interaction/awaiting-async-state.html and https://bunit.dev/docs/verification/async-assertion.html

Let me know if you have questions - it might be also worth sharing your component under test (in a minimal fashion) to know what is going on.
A word of advise: For testing purposes, try to mock out asynchronous stuff as much as you can and make sense in your test.
If you can create mocks/fakes that return Task.FromResult you don't have to deal with asynchronous stuff.

[rileyharris7]

Thank you! I have used WaitForState before, but in this case I didn't think it was necessary - turns out it is and that does solve the problem.

I do try to mock out everything asynchronous that I can, but there are cases where I want to simulate a service that has some async methods to test certain responses in my component. I'm still getting used to bUnit and Blazor as a whole, so I know not everything I'm doing is the best way of achieving my desired result. Thank you for being a helpful resource!