How to test user roles parsing in control code behind

[AFAde]

Hello,
in the code behind of a component we have the following code

public partial class MyComponent
            : ComponentBase,
              IDisposable
    {
        [CascadingParameter]
        public Task<AuthenticationState> AuthenticationStateTask { get; set; }

        protected override async Task OnInitializedAsync()
        {
            var authenticationState = AuthenticationStateTask.Result;
            if (authenticationState.User.IsInRole("myTestRole"))
            {
//DO something here if user has "myTestRole" role
                ...
            }

In my test, the code looks like the following

var context = new TestContext();
var authContext = context.AddTestAuthorization();
authContext.SetAuthorized("myUser");
authContext.SetRoles("myTestRole");

var component = ctx.Context.RenderComponent<MyComponent>();
...

When running the test, the condition authenticationState.User.IsInRole("myTestRole") is never true.

Could you please help me with that?

Thanks

[egil]

Hi @AFAde

Can you tell me what version of bUnit you are using?

[AFAde]

Hi @egil, I am using the 1.0.0-beta-11 version

[egil]

Hey @DarthPedro

Do you have a moment to help troubleshoot this problem? My reproduction confirms this:

CUT:

@using Microsoft.AspNetCore.Components.Authorization

Is in myTestRole = @isInRole

@code {
    private bool isInRole;

    [CascadingParameter]
    public Task<AuthenticationState> AuthenticationStateTask { get; set; }

    protected override async Task OnInitializedAsync()
    {
        var authenticationState = await AuthenticationStateTask;
        isInRole = authenticationState.User.IsInRole("myTestRole");
    }
}

Test:

public class AuthyTest : TestContext
{
    [Fact]
    public void TestName()
    {
        var authCtx = this.AddTestAuthorization();
        authCtx.SetAuthorized("egil");
        authCtx.SetRoles("myTestRole");

        var cut = RenderComponent<Authy>();

        cut.WaitForAssertion(() => cut.MarkupMatches("Is in myTestRole = true"));
    }
}

What I notice is that authenticationState.User in the component is of type ClainsPrincipal, not FakePrincipal.

[DarthPedro]

@egil yes, I will take a look at why the unexpected claims principal is getting used there. I will likely investigate early next week.

[egil]

Awesome, thanks.

I might have messed something up in with the changes in beta 11, but regardless, we need at least one test for this scenario, so i don't do this again another time 😂

[JoshuaRHolden]

I set my view up to check roles then I tried it with:
var cut = RenderComponent<CascadingAuthenticationState>(x => x.AddChildContent<Authy>());

and it seems like its working for me, I hit the breakpoint and had the role, presume this is fixed?

[egil]

Hi @JoshuaRHolden

Only partially. You are not supposed to be required to render your cut inside a CascadingAuthenticationState. That works be added automatically for you.