VS2015控制台运行单元测试遇Selenium ChromeDriver及文件读取问题

Hey there! Let's break down and fix these two issues you're facing—they're both rooted in a super common gotcha: different working directories when running tests in VS Test Explorer vs. the MSTest console command.

1. Excel Test Data File Not Found (Relative Path Issue) #

The problem here is that when you run tests via Test Explorer, the working directory is usually your project root or the bin/Debug folder. But when you use the MSTest console command, it defaults to a different directory (often a temporary folder under %TEMP% or VS's test runtime directory), so your relative path can't locate the Excel file.

Fixes: #

• Use absolute paths tied to your test assembly's location: Instead of hardcoding a relative path, fetch the directory where your test DLL is running from, then build the full path to your Excel file. Here's how to do it in C#:

  // Get the directory where your test assembly is located
  string assemblyDir = AppDomain.CurrentDomain.BaseDirectory;
  // Path to your Excel file (adjust the relative part to match your project structure)
  string excelFilePath = Path.Combine(assemblyDir, @"TestData\your-test-data.xlsx");
  

• Ensure the Excel file is copied to output: In your Visual Studio project, right-click the Excel file → Properties → set Copy to Output Directory to Copy always or Copy if newer. This ensures the file gets moved to the bin/Debug folder alongside your test DLL.

2. ChromeDriver.exe Not Found (Even Though It's in Debug Folder) #

Same root cause: the MSTest console isn't running from your bin/Debug directory, so it can't find chromedriver.exe when you use the default initialization (which looks in the current working directory).

Fixes: #

• Specify the ChromeDriver path explicitly: Use the same assembly directory trick to point directly to the driver file:

  string driverPath = Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "chromedriver.exe");
  IWebDriver driver = new ChromeDriver(driverPath);
  

• Switch to the Selenium ChromeDriver NuGet package: This is the most reliable approach. Install the Selenium.WebDriver.ChromeDriver NuGet package—it automatically copies the correct version of chromedriver.exe to your output directory, and the ChromeDriver constructor will automatically find it without needing a path:

  // No need to specify path after installing the NuGet package
  IWebDriver driver = new ChromeDriver();
  

• Run MSTest from the correct directory: Open your command prompt, navigate to your project's bin/Debug folder first, then run the MSTest command. For example:

  cd C:\YourProjectRoot\bin\Debug
  MSTest /testcontainer:YourTestAssembly.dll
  

Quick Recap #

Both issues boil down to working directory differences between Test Explorer and the MSTest console. By using paths relative to your test assembly's location (instead of the current working directory) or leveraging NuGet for driver management, you'll eliminate these inconsistencies.

内容的提问来源于stack exchange，提问作者Den Fyren