基于SpecRun+LeanFT+Selenium C#实现并行测试的技术咨询

Great question! Let’s break this down step by step since you’re dealing with a specific (and tricky) combo of SpecFlow+SpecRun, Selenium, and LeanFT.

First, let’s address the core restriction you noticed: LeanFT’s default browser attachment logic targets the first available Chrome instance, which breaks parallel runs. The fix here is to isolate each Selenium-managed Chrome instance with a unique debug port, then tell LeanFT to attach to that specific port for each test thread.

Here’s how to implement this:

• When initializing your ChromeDriver, configure a unique --remote-debugging-port argument for each thread (use a base port like 9222 plus the thread ID to avoid collisions):

int debugPort = 9222 + Thread.CurrentThread.ManagedThreadId;
ChromeOptions options = new ChromeOptions();
options.AddArgument($"--remote-debugging-port={debugPort}");
IWebDriver driver = new ChromeDriver(options);

• When attaching LeanFT to the browser, explicitly target this unique port instead of using the default attachment logic:

BrowserDescription browserDesc = new BrowserDescription();
browserDesc.Add("debug.port", debugPort.ToString());
Browser leanFtBrowser = Browser.Attach(browserDesc);

This way, each test thread’s Chrome instance has its own dedicated debug port, so LeanFT won’t try to attach to the same browser across parallel tests.

Adjusting your default.srprofile thread count won’t cause conflicts if you’ve implemented the port isolation above. But there are a few key things to keep in mind:

• Set your profile’s execution settings to enable parallelism, and use MTA apartment state (LeanFT/Selenium work better here):

<Execution parallel="true" threadCount="4"> <!-- Adjust thread count based on your system resources -->
  <TestThread ApartmentState="MTA" />
</Execution>

• Ensure no global/shared IWebDriver or Browser instances exist in your code. Each test scenario must create and manage its own instance to avoid cross-thread contamination.
• Don’t overload your system: Start with 2-3 threads first, then scale up. Too many concurrent Chrome instances will eat up memory and CPU, leading to flaky tests regardless of LeanFT.

SpecFlow doesn’t have built-in restrictions around LeanFT—it just maps Gherkin steps to your automation code. The key to making this work is thread-safe context management using SpecFlow’s dependency injection:

• Create a test context class to hold thread-specific driver/browser instances:

public class TestContext
{
    public IWebDriver SeleniumDriver { get; set; }
    public Browser LeanFtBrowser { get; set; }
}

• Inject this context into your step definitions, so each thread gets its own instance:

[Binding]
public class WebSteps
{
    private readonly TestContext _testContext;

    public WebSteps(TestContext testContext)
    {
        _testContext = testContext;
    }

    [Given(@"I launch Chrome with LeanFT integration")]
    public void LaunchChromeWithLeanFt()
    {
        // Initialize driver and LeanFT browser as shown earlier, store in _testContext
        int debugPort = 9222 + Thread.CurrentThread.ManagedThreadId;
        ChromeOptions options = new ChromeOptions();
        options.AddArgument($"--remote-debugging-port={debugPort}");
        _testContext.SeleniumDriver = new ChromeDriver(options);

        BrowserDescription browserDesc = new BrowserDescription();
        browserDesc.Add("debug.port", debugPort.ToString());
        _testContext.LeanFtBrowser = Browser.Attach(browserDesc);
    }

    [AfterScenario]
    public void Cleanup()
    {
        // Properly dispose resources to avoid leaks
        _testContext.LeanFtBrowser?.Close();
        _testContext.SeleniumDriver?.Quit();
    }
}

This ensures each test scenario runs with its own isolated Selenium/LeanFT stack, which is critical for parallel execution.

• Test incrementally: Start with 2 parallel threads to validate the port isolation works before scaling up.
• Add logging: Include thread IDs and debug ports in your test logs to quickly diagnose any attachment conflicts.
• Use recent LeanFT versions: Older versions had stricter limitations on multi-instance attachment—make sure you’re on a release that supports targeting debug ports.

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