You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to execute a simple test from VSTest Explorer doesn't work.
Keep seeing this error message in the html report,
Execution framework error: TechTalk.SpecRun.Framework.SpecRunException: At least one test thread aborted. ---> System.ComponentModel.Win32Exception: The system cannot find the file specified. at TechTalk.SpecRun.Framework.TestThread.UnpackTestThreadExecutorInfoResult(IResult`1 testThreadExecutorInfoResult) at TechTalk.SpecRun.Framework.TestThread.InitializeTestThreadExecutor(IAssemblyReference testAssembly, ExecutionModelSettings executionModelSettings, String testTarget) at TechTalk.SpecRun.Framework.TestThread.GetThreadExecutor(IAssemblyReference testAssembly, ExecutionModelSettings executionModelSettings, String testTarget) at TechTalk.SpecRun.Framework.TestThread.GetThreadExecutorForTestItem(TestItem testItem) at TechTalk.SpecRun.Framework.TestThread.RunNonEmptyTestSuite(CancellationToken cancellationToken, TestThreadState testThreadState) at TechTalk.SpecRun.Framework.TestThread.Run(ITestExecutionManager executionManagerForRun, CancellationToken cancellationToken) at TechTalk.SpecRun.Framework.AsyncTestThreadRunner.RunSync(TestExecutionManager executionManager, CancellationToken cancellationToken) --- End of inner exception stack trace ---
Steps to Reproduce
The text was updated successfully, but these errors were encountered:
@SabotageAndi - https://github.com/venkatrao-rgare/specflow-vs2019, at this stage i am not sure if this is an issue with specflow or vs2019 or some setup in my machine. I am fairly new to specflow and visual studio. Please try this project and let me know if this works for you.
@venkatrao-rgare I could reproduce your issue. Your project is fine.
For me, the problem was, that the test explorer was set to x86, but I don't have .NET Core for x86 installed. I only have x64 installed.
You can see this in the logfile. There is an entry like Executing test executor at 'C:\Program Files (x86)\dotnet\dotnet.exe' 'exec ' .....
After changing to x64, I was able to execute the tests successfully.
SpecFlow Version:
Used Test Runner
Version number:
Project Format of the SpecFlow project
packages.config
<PackageReference>
tags.feature.cs files are generated using
SpecFlow.Tools.MsBuild.Generation
NuGet packageSpecFlowSingleFileGenerator
custom toolVisual Studio Version
Enable SpecFlowSingleFileGenerator Custom Tool
option in Visual Studio extension settingsAre the latest Visual Studio updates installed?
Version 16.4.2
.NET Framework:
Test Execution Method:
<SpecFlow> Section in app.config or content of specflow.json
Repro Project
csproj file
Issue Description
Trying to execute a simple test from VSTest Explorer doesn't work.
Keep seeing this error message in the html report,
Execution framework error: TechTalk.SpecRun.Framework.SpecRunException: At least one test thread aborted. ---> System.ComponentModel.Win32Exception: The system cannot find the file specified. at TechTalk.SpecRun.Framework.TestThread.UnpackTestThreadExecutorInfoResult(IResult`1 testThreadExecutorInfoResult) at TechTalk.SpecRun.Framework.TestThread.InitializeTestThreadExecutor(IAssemblyReference testAssembly, ExecutionModelSettings executionModelSettings, String testTarget) at TechTalk.SpecRun.Framework.TestThread.GetThreadExecutor(IAssemblyReference testAssembly, ExecutionModelSettings executionModelSettings, String testTarget) at TechTalk.SpecRun.Framework.TestThread.GetThreadExecutorForTestItem(TestItem testItem) at TechTalk.SpecRun.Framework.TestThread.RunNonEmptyTestSuite(CancellationToken cancellationToken, TestThreadState testThreadState) at TechTalk.SpecRun.Framework.TestThread.Run(ITestExecutionManager executionManagerForRun, CancellationToken cancellationToken) at TechTalk.SpecRun.Framework.AsyncTestThreadRunner.RunSync(TestExecutionManager executionManager, CancellationToken cancellationToken) --- End of inner exception stack trace ---
Steps to Reproduce
The text was updated successfully, but these errors were encountered: