Windows 11 O.S. - Test Execute not correctly running

Question

Hi,with Windows 11 O.S. I'm falling within some issues for the Azure DevOps release pipeline execution, that randomically fails with an "Unable to connect to TestExecute error".This error happens when TestExecute is sometimes not correctly started, that is: it is shown within the Task Manager but is not appearing within the running programs:The issue can be resolved after several attempts, by trying to kill the process and then rerun it but, in the meanwhile, the automatic tests within the release pipeline cannot be executed since the "Unable to connect" error is raised.Note that the machine contains only the Administrator user, so there are no other users connected.This issue had never happened by using Windows 10.Has anyone encountered this issue and how do you have resolved it?Thanks!Simona

rraghvani · Answer

I'm not sure how your TestExecute is launched, but are you using the /exit parameter? This parameter will ensure that TestExecute is fully closed once all tests are completed.

simonaferrara · Answer

From release pipeline, I'm using VSTest task, as this example:If I run it manually (and the issue is replicated also manually), I simply double click TestExecute.exe by running it as administrator.

rraghvani · Answer

In the task you have shown, is there a way of adding command line parameters, which can be used for TestExecute?
For example (not sure if it will work!),
- task: VSTest@2
  displayName: 'Run TestExecute tests'
  inputs:
    testSelector: 'testAssemblies'
    testAssemblyVer2: '**\*TestExecute*.exe'
    searchFolder: '$(System.DefaultWorkingDirectory)'
    runSettingsFile: '$(System.DefaultWorkingDirectory)\TestRunSettings.runsettings'
    otherConsoleOptions: '/param1 value1 /param2 value2'
    diagnosticsEnabled: true
or
- task: CmdLine@2
  displayName: 'Run TestExecute with Parameters'
  inputs:
    script: '"C:\Program Files (x86)\SmartBear\TestExecute\TestExecute.exe" /Project:"$(Build.SourcesDirectory)\MyTestProject.pjs" /run /exit /param1 value1 /param2 value2'

&nbsp;

marsha_r · Answer

Do your TestComplete and TestExecute versions still match?

simonaferrara · Answer

I've got only TestExecute version installed on that machine (no TestComplete installed) and it is the following: 15.68.8.11 x64 .

Forum Discussion

Windows 11 O.S. - Test Execute not correctly running

10 Replies

Recent Discussions

WinForms application crashes on "save as" dialog

Cannot Open Sys Object Tree

Azure DevOps Pipelines - "Headless" VMs

Related Content

Failed to execute 'fetch' on 'Window': Invalid name

Windows schedular fails launching Test Execute

The window was destroyed during method execution.