Using Theory with MemberData and RenderFragments

[SQL-MisterMagoo]

Watching @egil on Twitch has inspired me to finally learn bUnit.

I saw the horrible formatting issues on stream caused by using a razor file to write tests that use RenderFragments and thought - why not split them out to razor + cs code-behind and have found this works:

In Test1.razor (naming huh) I have my RenderFragments and a method Data to provide those data items to the test:

@inherits TestContext
@code{
	static RenderFragment rfcut1 => @<HelloSayer /> ;
	static RenderFragment rftest1 => @<h1>Hello</h1> ;

	static RenderFragment rfcut2 => @<HelloSayer Name="Magoo" /> ;
	static RenderFragment rftest2 => @<h1>Hello Magoo</h1> ;

	public static IEnumerable<object[]> Data =>
        new List<object[]>
        {
            new object[] {rfcut1, rftest1},
            new object[] {rfcut2, rftest2},
        };
}

And then, in the Test1.razor.cs file, I can write my tests with proper editor support:

Test1.razor.cs

public partial class Test1
{

    [Theory, MemberData(nameof(Data))]
    public void SimpleTests(RenderFragment rfcut,RenderFragment rfexpected)
    {
        var cut = Render(rfcut);
        cut.MarkupMatches(rfexpected);
    }
}

I didn't find any mention of using MemberData with RenderFragments, so thought I would share :)

x Magoo

[egil]

Thank you for sharing this.

Personally I prefer to keep all things involving a test as close together as possible, which is why I suffer through the current editor experience. Keeping things close together makes the test much easier to read and comprehend, for everybody else and myself the next time I have read the code.

Update: i do see a use for this if e.g. multiple test cases need the same render fragments as input, so this can definitely be useful in certain situations.