private cascanding parameter

[Julien-Marpault]

I'm trying to test a component using Edit context:

IRenderedComponent<InputEmail> cut = Render<InputEmail>(parameters =>
        {
            parameters.Add(p => p.CurrentEditContext, editContext);
            parameters.Bind(p => p.Value, email, newValue => email = newValue ?? string.Empty);
            parameters.Add(p => p.ValidationFor, () => email);
        });

The problem her is CurrentEditContext is a private parameter.

Is the a way to test it ? Or do I need to modify the visibility of CuurentEditContext (I prefer no if possible).

Thanks

[linkdotnet]

Now out of the box and on top of my head there is no other way.

but here is my personal salt to the topic: it seems you want to test an internal state rather than observable behaviour.

probably that context (depending on its value) does something that is observable from the outside. This is probably what you wanna test.

[Julien-Marpault]

Actually I made an <InputEmail> component and I want to test it.
The point here, is I have included Validation inside the component and I need the EditContext for that reason.

Here's the code of the component:

@inherits InputBase<string>

<div class="input-wrapper">
    <input @attributes="@AdditionalAttributes" class="border-bottom-dark @CssClass" @bind-value="CurrentValue" @bind-value:event="oninput" @oninput:stopPropagation required />
    <label>@(string.IsNullOrEmpty(Label) ? "Email" : Label)</label>
    @if (ShowSendIcon)
    {
        if (SendIcon == null)
        {
            <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512" @onclick="Send" style="position:absolute;height:1rem;right:1.25rem;bottom:3rem;cursor:pointer;">
                <path d="M476 3.2L12.5 270.6c-18.1 10.4-15.8 35.6 2.2 43.2L121 358.4l287.3-253.2c5.5-4.9 13.3 2.6 8.6 8.3L176 407v80.5c0 23.6 28.5 32.9 42.5 15.8L282 426l124.6 52.2c14.2 6 30.4-2.9 33-18.2l72-432C515 7.8 493.3-6.8 476 3.2z" />
            </svg>
        }
        else
        {
            @SendIcon
        }
    }
    @if (ValidationFor != null)
    {
        <ValidationMessage For="@ValidationFor" />
    }
</div>

And if the EditContext is not provided I get this error message:
System.InvalidOperationException : Microsoft.AspNetCore.Components.Forms.ValidationMessage1[System.String] requires a cascading parameter of type EditContext. For example, you can use Microsoft.AspNetCore.Components.Forms.ValidationMessage1[System.String] inside an EditForm.

I thing I will consider to include my component in an EditForm for the test id it's not possible ton set private CascadingPArameters.
It should be useful but if not possible, I will find a workaround.

[linkdotnet]

I think your approach is the right way to go: Add an EditForm around. Of course, you are free to wrap your component in whatever you want inside your test. You can create separate test components that create an EditContext and have your InputEmail as child component.

You can, alternatively, also add a EditContext as part of the RenderTree: https://bunit.dev/docs/providing-input/root-render-tree.html

[Julien-Marpault]

I think I will give a try to root component. Seems more flexible.

Thank you.

[Julien-Marpault]

Adding EditContext to Root Component is perfect.