本地有Visual Studio，如何在无VS的局域网远程机器执行C#单元测试？

Yes, absolutely! You don’t need the full Visual Studio IDE installed to execute C# unit tests. The .NET ecosystem has lightweight tools that let you run tests directly from the command line, no IDE required. Let’s break down how to make this work, plus the minimum requirements you’ll need.

Step-by-Step Implementation Process #

Here’s a straightforward workflow to set this up for your remote machines:

• Prep test assets locally first
  In your Visual Studio environment, confirm your test project compiles and runs tests successfully. Then head to your test project’s output directory (usually bin/Debug/net[version]/ or bin/Release/net[version]/). This folder holds your compiled test DLL, all dependency files, and test framework adapters (like xUnit/NUnit/MSTest support components)—don’t skip any of these.
• Install required components on remote machines
  You have two lightweight options here:
  1. Full .NET SDK: Includes the runtime, test tools, and compiler. It’s the easiest pick if you might need to build code later, though it’s a larger download.
  2. .NET Runtime + .NET Test SDK: A more minimal choice. Install the runtime matching your test project’s .NET version, then add the Test SDK via dotnet tool install --global dotnet-test-sdk (or use official installer packages).
• Copy test assets to the remote machine
  Transfer the entire output folder from your local machine to a directory on the remote machine (e.g., C:\TestAssets on Windows or /opt/testassets on Linux). Make sure every file is included—dependencies and test framework files are critical for tests to run.
• Execute the tests remotely
  Open a command prompt/PowerShell (Windows) or terminal (Linux/macOS) on the remote machine, navigate to the test folder, and run:

  dotnet test
  

  To target a specific test DLL directly, use:

  dotnet test YourTestAssembly.dll
  

  You can add flags to customize output, like --logger "trx" to generate a structured test report, or --filter "Category=Integration" to run only specific test groups.
• Review results
  The dotnet test command will print a summary of passed/failed tests right in the console. If you generated a trx report, you can open it in Visual Studio later (or parse it with other tools) for deeper insights.

Minimum System & Software Requirements #

System Requirements #

• Windows: Windows 10 1809+ / Windows Server 2019+ (for .NET 6+; older .NET versions support earlier releases like Windows 8.1+)
• Linux: Ubuntu 18.04+, Debian 10+, RHEL 8+, or other distributions officially supported by your target .NET version
• macOS: macOS 10.15+ (for .NET 6+)
• Hardware: At least 2GB of RAM (4GB recommended), plus enough disk space to store test assets and temporary files (usually a few hundred MB minimum)

Software Requirements #

• Core requirement: The .NET Test SDK (included with the full .NET SDK, or installable separately if you only have the .NET Runtime)
• Test framework compatibility: Your test project must use a framework supported by dotnet test (MSTest, xUnit, NUnit are all fully supported). The necessary adapter files will be in your local output folder—just copy them over to the remote machine.
• Matching .NET versions: The remote machine’s installed .NET runtime/SDK must match the version your test project was compiled against (e.g., if you built for .NET 7, the remote machine needs .NET 7 components installed).

Quick Tips #

• If your tests rely on external resources (databases, network services, local files), ensure the remote machine has access to those resources and the necessary permissions to interact with them.
• For automated runs, you can set up scripts or use PowerShell remoting to execute dotnet test commands remotely without manually logging into each machine.

内容的提问来源于stack exchange，提问作者Snehal Gokhale