如何将Selenium WebDriver C#-MSUnit测试集成到Jenkins作为CI/CD环节运行

Got it, let's walk through how to integrate your C# Selenium WebDriver tests (using MSUnit) into Jenkins as part of your CI/CD pipeline. I've done this a few times, so here's a step-by-step breakdown that should work smoothly:

First, make sure your Jenkins server has all the tools needed to run your tests:

• .NET SDK: Install the version matching your project (e.g., .NET 6/7/8). You can manage this via Jenkins' Global Tool Configuration, or install it directly on the server. For older .NET Framework projects, you'll need MSBuild instead.
• Jenkins Plugins: Install two key plugins:
  • MSBuild Plugin: Helps build your .NET projects
  • xUnit Plugin: Parses MSUnit test results and generates visual reports in Jenkins

Before moving to Jenkins, ensure your tests run flawlessly on your machine:

• Double-check NuGet dependencies: Make sure you have Selenium.WebDriver, Selenium.Support, Microsoft.VisualStudio.TestPlatform.TestAdapter, and Microsoft.VisualStudio.TestPlatform.Client installed.
• Use WebDriverManager.Net: This NuGet package automatically downloads the correct browser driver (Chrome/Firefox/etc.) at runtime, so you don't have to manually configure driver paths on Jenkins. Add this code to your test initialization:

  WebDriverManager.DriverManager().SetUpDriver(new ChromeConfig()); // For Chrome; use FirefoxConfig for Firefox
  

• Verify MSUnit annotations: Ensure your test classes are marked with [TestClass] and test methods with [TestMethod] so MSUnit can detect them.

You have two main options here—pick the one that fits your workflow:

Option A: Freestyle Project (Quick & Simple) #

1. Create a new Freestyle project in Jenkins.
2. Source Code Management: Link your Git repo, add credentials, and select the branch you want to build.
3. Build Steps:
   • Add an Execute Windows Batch Command (for Windows Jenkins) or Execute Shell (for Linux/macOS) to build your project:

     # For .NET Core/.NET 5+
     dotnet build YourTestProject.sln --configuration Release
     

     For .NET Framework:

     msbuild YourTestProject.sln /p:Configuration=Release /p:Platform="Any CPU"
     

   • Add another build step to run tests and generate an xUnit-formatted report (so Jenkins can parse results):

     dotnet test YourTestProject.csproj --configuration Release --logger "xunit;LogFilePath=../../TestResults/test-results.xml"
     

     Adjust the file path to ensure Jenkins can access the generated XML report.
4. Post-build Action: Add Publish xUnit test result report, and enter **/TestResults/test-results.xml in the Test report XMLs field. This will display pass/fail rates and detailed test logs in Jenkins.

Option B: Jenkins Pipeline (For Complex CI/CD) #

1. Create a new Pipeline project, select Pipeline script from SCM, and link your repo.
2. Add a Jenkinsfile to your repo root with this example code (adjust for your project name and OS):

   pipeline {
       agent any
       stages {
           stage('Build Project') {
               steps {
                   script {
                       // Use 'sh' instead of 'bat' if Jenkins is on Linux/macOS
                       bat 'dotnet build YourTestProject.sln --configuration Release'
                   }
               }
           }
           stage('Run Selenium Tests') {
               steps {
                   script {
                       bat 'dotnet test YourTestProject.csproj --configuration Release --logger "xunit;LogFilePath=TestResults/test-results.xml"'
                   }
               }
               post {
                   always {
                       // Publish test results regardless of pass/fail
                       xunit (
                           tools: [XUnit2(defaultPattern: '**/TestResults/test-results.xml')]
                       )
                   }
               }
           }
       }
   }
   

Jenkins servers usually don't have a GUI, so you need to run Selenium browsers in headless mode:

• For Chrome, add these options when initializing the driver:

  var options = new ChromeOptions();
  options.AddArgument("--headless=new"); // Newer Chrome headless mode
  options.AddArgument("--disable-gpu");
  options.AddArgument("--no-sandbox"); // Required for Linux environments
  var driver = new ChromeDriver(options);
  

• For Firefox, use FirefoxOptions and add the --headless argument.

If tests pass locally but fail on Jenkins:

• Check that the .NET version on Jenkins matches your local environment (run dotnet --version in a Jenkins build step to verify).
• Review Jenkins build logs for errors like driver download failures or browser launch issues.
• Ensure the URLs your tests target are accessible from the Jenkins server (e.g., if testing a local API, make sure Jenkins can reach it).
• Print environment variables (e.g., echo %PATH% on Windows, echo $PATH on Linux) to confirm driver paths are set correctly.

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