Investigate and fix issues for cross-platform runs

[JanKrivanek]

Problem

When running unit tests on WSL or docker (see #729 for more details), some unit tests (currently around 90) are failing - mostly due to different file convetions on host and target OSes.

Proposed solution

Try to investigate and fix those issues. If there is legitimate reason for failures for the crossplatform scenario - try to exclude them (e.g. detect virtualized run and skip tests programatically: xunit/xunit#2073)

[maksNechyporuk]

Hello. I have a similar problem. When I try run tests in docker I received following error
Error Message: 2023-02-02 09:03:30 VerifyException : Directory: /app/src/Tests/Limit.IntegrationTests/WebApiTests 2023-02-02 09:03:30 New: 2023-02-02 09:03:30 - Received: ShouldReturnSuccessResponse.received.txt 2023-02-02 09:03:30 Verified: ShouldReturnSuccessResponse.verified.txt

But file ShouldReturnSuccessResponse.verified.txt exists in the inside of docker container

This is my test
`

    var httpClient = _factory.CreateClient(); 
    var time = DateTime.UtcNow;

    var request = TestData.GetLimitRequest(time);

    var response = await httpClient.PostAsJsonAsync("/api/get-limit", request);

    var responseObject = await GetResponseFromHttpContentAsync(response.Content);

    response.StatusCode.Should().Be(HttpStatusCode.OK);
    await Verify(responseObject).IgnoreMembers("Id");        

`
I use the following packages

    <PackageReference Include="Microsoft.AspNetCore.Mvc.Testing" Version="7.0.2" />
    <PackageReference Include="Verify.Xunit" Version="19.8.1" />
    <PackageReference Include="Xunit.Di" Version="2.4.5" />
    <PackageReference Include="xunit.extensibility.core" Version="2.4.2" />
    <PackageReference Include="xunit" Version="2.4.2" />
    <PackageReference Include="xunit.runner.visualstudio" Version="2.4.5">
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
      <PrivateAssets>all</PrivateAssets>
    </PackageReference>

can you help me?

[JanKrivanek]

If you accept the changes (rename the ShouldReturnSuccessResponse.received.txt to ShouldReturnSuccessResponse.verified.txt and copy it from docker to your snapshot files) - is the error still present?

Is it possible that the snapshot file was generated on windows and content differs from what is produced in unix?
If yes - is the difference given by your code, or is the difference in some nonprintable chars (line endings, BOM etc)?

[SimonCropp]

can anyone provide me with a failing test in a PR?

[OskarKlintrot]

What distro/images is it failing on? I've been using Verify for almost a year now in https://github.com/OskarKlintrot/UpdatR that uses Ubuntu on Github Actions and there everything works fine. I also use it on Azure DevOps with Ubuntu and that also works fine.

[JanKrivanek]

@SimonCropp this bug was meant for tests built on Windows and then run on unix while having access to original build location via mount drive - either via WSL or test docker run - achieving this in CI would require significant effort.

This is unrelated to building and executing tests on a single platform (which are the cases in other comments)

[devantler]

I am also noticing issues related to cross-platform runs that seems related to this issue and an older one that have been closed #654. In particular my unit tests are failing when I target ubuntu-latest in my GitHub Actions. It works fine locally (MacOS) and targeting macos-latest in GitHub Actions.

Packages in use:

<PackageReference Include="Verify.SourceGenerators" Version="2.1.0" />
<PackageReference Include="Verify.XUnit" Version="19.10.0" />

A stack trace can be seen here:

Error Message:
[606](https://github.com/devantler/data-mesh/actions/runs/4258183229/jobs/7409142988#step:7:607)
   System.ArgumentNullException : Value cannot be null. (Parameter 'path')
[607](https://github.com/devantler/data-mesh/actions/runs/4258183229/jobs/7409142988#step:7:608)
  Stack Trace:
[608](https://github.com/devantler/data-mesh/actions/runs/4258183229/jobs/7409142988#step:7:609)
     at VerifyTests.VerifySourceGenerators.Convert(GeneratorDriverRunResult target, IReadOnlyDictionary`2 context) in C:\projects\verify-sourcegenerators\src\Verify.SourceGenerators\VerifySourceGenerators.cs:line 56
[609](https://github.com/devantler/data-mesh/actions/runs/4258183229/jobs/7409142988#step:7:610)
   at VerifyTests.VerifySourceGenerators.Convert(GeneratorDriver target, IReadOnlyDictionary`2 context) in C:\projects\verify-sourcegenerators\src\Verify.SourceGenerators\VerifySourceGenerators.cs:line 86
[610](https://github.com/devantler/data-mesh/actions/runs/4258183229/jobs/7409142988#step:7:611)
   at VerifyTests.VerifierSettings.<>c__DisplayClass150_0`1.<RegisterFileConverter>b__0(T o, IReadOnlyDictionary`2 context) in /_/src/Verify/Splitters/Settings_Typed.cs:line 29
[611](https://github.com/devantler/data-mesh/actions/runs/4258183229/jobs/7409142988#step:7:612)
   at VerifyTests.VerifierSettings.<>c__DisplayClass151_0`1.<RegisterFileConverter>b__0(Object o, IReadOnlyDictionary`2 context) in /_/src/Verify/Splitters/Settings_Typed.cs:line 38
[612](https://github.com/devantler/data-mesh/actions/runs/4258183229/jobs/7409142988#step:7:613)
   at VerifyTests.InnerVerifier.Verify(Object target) in /_/src/Verify/Verifier/InnerVerifier_Object.cs:line 62
[613](https://github.com/devantler/data-mesh/actions/runs/4258183229/jobs/7409142988#step:7:614)
   at VerifyXunit.Verifier.<>c__DisplayClass7_0.<<Verify>b__0>d.MoveNext() in /_/src/Verify.Xunit/Verifier.cs:line 74
[614](https://github.com/devantler/data-mesh/actions/runs/4258183229/jobs/7409142988#step:7:615)
--- End of stack trace from previous location ---
[615](https://github.com/devantler/data-mesh/actions/runs/4258183229/jobs/7409142988#step:7:616)
--- End of stack trace from previous location ---

The full build that fails can be seen here: https://github.com/devantler/data-mesh/actions/runs/4258183229/jobs/7409142988

[SimonCropp]

please submit a failing pe