No tests after parsing intermediate results on v0.10.0-dev-366d0c7

[rudiejd]

First of all, thank you so much for the plugin! I'm excited to move my entire workflow into neovim. I have the following situation on Neovim v0.10.0-dev-366d0c7. Essentially, the intermediate results have valid output, but the plugin is unable to parse the output. Here is the log (censored some test names since it's a work project)

INFO | 2023-10-23T09:58:58Z-0400 | ...are/nvim/lazy/neotest-dotnet/lua/neotest-dotnet/init.lua:196 | neotest-dotnet: Found X test results when parsing TRX file: /tmp/nvim.jd/MmVrVZ/0.trx
DEBUG | 2023-10-23T09:58:58Z-0400 | ...are/nvim/lazy/neotest-dotnet/lua/neotest-dotnet/init.lua:203 | neotest-dotnet: Intermediate Results: 
DEBUG | 2023-10-23T09:58:58Z-0400 | ...are/nvim/lazy/neotest-dotnet/lua/neotest-dotnet/init.lua:204 | { {
    raw_output = "passed",
    status = "passed",
    test_name = "foo
    }... (more like this)
} }
DEBUG | 2023-10-23T09:58:58Z-0400 | ...are/nvim/lazy/neotest-dotnet/lua/neotest-dotnet/init.lua:209 | neotest-dotnet: Neotest Results after conversion of Intermediate Results: 
DEBUG | 2023-10-23T09:58:58Z-0400 | ...are/nvim/lazy/neotest-dotnet/lua/neotest-dotnet/init.lua:210 | {}

These tests show as failing, despite the output of dotnet test showing that they succeed. This is with NUnit if that is relevant.

[Issafalcon]

Hi @rudiejd - Thanks for raising an issue.

I understand you're limited in what information you can provide from your work project, but there isn't enough for me to go on here I'm afraid.

If you could put together a small sample project that contains a test structure that's similar to your use case, and that also produces the issue, that would be a good first step.

[Issafalcon]

Closing this issue due to inactivity.

Please feel free to raise another issue once more comprehensive reproduction steps can be provided.