System cannot find file specified with NUnit3 console and testparam

Question

I tried to run flaUiTests with the command prompt with the following command:

pathToConsole\nunit3-console.exe pathToApp\App.dll --testparam:App=pathToExecutable\App.exe

In the testcode I use the testparam with te following code:

string lParameterPathExecutable = TestContext.Parameters["App"];

I tested if the command prompt can find al the files and he can. Anyway, I get still the error: System.ComponentModel.Win32Excetion: The system cannot find the file specified.

Does anyone know what the problem is? What it's wrong with this command? The testcode is in VisualStudio2019 and the version of NUnit3-console is 3.12.0.

Edit: The nunit3-console can be found. The nunit3-console runs I think. This is the testresult:

System.ComponentModel.Win32Exception : The system cannot find the file specified
--Win32Exception
The system cannot find the file specified
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at NUnit.Engine.Services.TestAgency.CreateRemoteAgent(TestPackage package, Int32 waitTime)
   at NUnit.Engine.Runners.ProcessRunner.CreateAgentAndRunner()
   at NUnit.Engine.Runners.ProcessRunner.RunTests(ITestEventListener listener, TestFilter filter)

Test Run Summary
  Overall result: Failed
  Test Count: 0, Passed: 0, Failed: 0, Warnings: 0, Inconclusive: 0, Skipped: 0
  Start time: 2021-02-10 21:26:08Z
    End time: 2021-02-10 21:26:08Z
    Duration: 0.145 seconds

Results (nunit3) saved as TestResult.xml

Answer 1

I solved this issue by running the runner directly from the nuget package:

packages\\NUnit.ConsoleRunner.3.15.0\\tools\\nunit3-console.exe [params]

---

One of my collegues added this workflow before, which doesn't work with newer versions of NUnit.ConsoleRunner:

1. post-build event: copy "$(SolutionDir)packages\NUnit.ConsoleRunner.3.15.0\tools\*.*" "$(TargetDir)
2. Run bin\\Release\\nunit3-console.exe [params]

Answer 2

I am experiencing the same issue after upgrading to version 3.12.0. Downgrading to 3.11.1 solved the issue, however not a permanent fix.