Decimal separator inconsistency (MarkupMatches) causes test failure when pushed to Azure

[BenjoWatcher]

The bug is related to a difference in decimal separators between the local environment and Azure. When running a test that expects a comma as a decimal separator, the test fails when pushed to Azure, which requires a point as the decimal separator. This causes the test to produce an error message indicating a difference near ".4" in the expected value "5,4". To reproduce this issue, follow these steps:

1. Run the test locally and ensure that it passes.
2. Push the test to Azure and run it.
3. Observe that the test fails with an error message indicating a difference near ".4" in the expected value "5,4".

Example:

    [Test]
    public void ComponentShouldGetDropSequence()
    {
        // Act
       var component = RenderComponent<FwdBlazorApp.Pages.DataViewer.DataViewer> 
       (parameters=>parameters.AddCascadingValue(RenderComponent<MainLayout>().Instance));
        
        // Assert
        component.FindAll("td")[0].TextContent.MarkupMatches("5,4");
        component.FindAll("td")[1].TextContent.MarkupMatches("43,3");
        component.FindAll("td")[2].TextContent.MarkupMatches("50,4");
        component.FindAll("td")[3].TextContent.MarkupMatches("32,08");
    }

Component under test

    <RowTemplate>
        <MudTd DataLabel="Station">5,4</MudTd>
        <MudTd DataLabel="Drop ID">43,3</MudTd>
        <MudTd DataLabel="Force">50,4</MudTd>
        <MudTd DataLabel="Stress">32,08</MudTd>
    </RowTemplate>

Results in this output (Locally):

Results in this output (Azure):

Version info:

• bUnit version: 1.18.4

Workaround:
Although there is a workaround available, it is not an optimal solution. As such, it would be prudent to address the underlying issue with MarkupMatches() to fully resolve the bug.

        var td3 = component.FindAll("td")[0].TextContent;
        Assert.That(Convert.ToDouble(td3),Is.EqualTo(5.4));
        
        var td4 = component.FindAll("td")[1].TextContent;
        Assert.That(Convert.ToDouble(td4),Is.EqualTo(43.3));
        
        var td5 = component.FindAll("td")[2].TextContent;
        Assert.That(Convert.ToDouble(td5),Is.EqualTo(50.4));
        
        var td6 = component.FindAll("td")[3].TextContent;
        Assert.That(Convert.ToDouble(td6),Is.EqualTo(32.08));

[egil]

Converted this to a QA discussion since it is not a bug/problem in bUnit.

When you run your tests, you can specify the "culture" the runtime should be using, so it is independent of the operating system you are using.

How to approach this depends on the testing framework you are using. For example, if you're using xUnit, you can add the UseCultureAttribute to your project, as defined here:

https://github.com/xunit/samples.xunit/blob/master/UseCulture/UseCultureAttribute.cs

To use it:

[Fact]
[UseCulture("en-US")]
public void MyTest()
{
    // ...
}

[BenjoWatcher]

Thanks for the answer.

For NUnit it is SetCulture instead.