Add support for .runsettings with vstest

[samwcoulter]

Edit: This PR adds support for (automatically) selecting a .runsettings file that is located in the test project directory. If more than one .runsettings file is present, the user is given a choice via vim.ui.select. The user can also specify a custom .runsettings selector function via the plugin configuration. I have also added a configuration option for the vstest client communication timeout.

Notably missing from this PR are automated tests, and MTP/.testconfig.json support. My current platform (linux/ubuntu) does not yet have an easy to obtain release of .NET10, but I will open a new PR to add MTP support once I can easily test it locally.

WIP PR, looking for feedback.

MTP has abandoned the .runsettings format in favour of testconfig.json, so we will need to add client specific support for each.

[Nsidorenco]

Super nice that you’re implementing this!
I’m on vacation for the next couple of weeks so I won’t be able to look at this until then 😄

[froats]

I have been trying this with following config:

require("neotest").setup({
      log_level = vim.log.levels.TRACE,
      adapters = {
        require("neotest-vstest")({
          settings_selector = function(project_dir)
            -- Try to find .runsettings file in project root or common locations
            local runsettings_paths = {
              os.getenv("GIT_WORK_TREE") .. "/.runsettings",
            }
            for _, path in ipairs(runsettings_paths) do
              if vim.fn.filereadable(path) == 1 then
                vim.notify("Using runsettings file: " .. path)
                return path
              end
            end
            return nil -- let the adapter choose default
          end,
        }),
      },

Then in my .runsettigns:

<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
  <!-- Coverlet collector configuration for automatic code coverage -->
  <DataCollectionRunSettings>
    <DataCollectors>
      <DataCollector friendlyName="XPlat code coverage">
        <Configuration>
          <!-- Output format: lcov for neotest compatibility -->
          <Format>lcov</Format>
          
          <!-- Output filename for coverage data -->
          <CoverletOutputFileName>coverage.info</CoverletOutputFileName>
          
          <!-- Output coverage.info to test project directory -->
          <CoverletOutputDirectory>./app/tests/BasicService.Tests</CoverletOutputDirectory>

          <!-- Include only the main project, exclude test projects -->
          <Include>[BasicService]*</Include>
          <Exclude>[BasicService.Tests]*,[*.Tests]*,*Tests.dll</Exclude>

          <!-- Exclude compiler-generated and auto-property code -->
          <ExcludeByAttribute>GeneratedCodeAttribute,CompilerGeneratedAttribute,ObsoleteAttribute,ExcludeFromCodeCoverageAttribute</ExcludeByAttribute>

          <!-- Skip auto-properties from coverage -->
          <SkipAutoProps>true</SkipAutoProps>

          <!-- Use source linking for better coverage analysis -->
          <UseSourceLink>true</UseSourceLink>
        </Configuration>
      </DataCollector>
    </DataCollectors>
  </DataCollectionRunSettings>

  <!-- Run configuration -->
  <RunConfiguration>
    <TreatNoTestsAsError>false</TreatNoTestsAsError>
  </RunConfiguration>
</RunSettings>

No file coverage is created though... Could you help me with this?

[samwcoulter]

@froats Hmm, I can try to debug.

Is your custom settings selector finding the right file?

If you run the tests with dotnet test --settings <PATH_TO_RUNSETTINGS> <PATH_TO_TESTPROJECT_CSPROJ> Is the coverage generated?

[samwcoulter]

@froats I found an issue when a customs settings selector is used. Please try the latest revision from my fork.

[froats]

Hi, it is taking the file properly now, the coverage is still not being created though.. I will have to check why

[Nsidorenco]

This looks really good, thank you for contributing!

Did you learn anything of why your coverage file was not generated @froats?

[Nsidorenco]

I'll go ahead and merge this now. Thanks!