Running TestExecute from Powershell - TestExecute.exe is not a valid project.
SOLVED- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Running TestExecute from Powershell - TestExecute.exe is not a valid project.
Hi all
I'm using TestExecute 14.10.1042.11 x86 with Windows 10 1903 build 18362.295.
When opening powershell (32 or 64 bit) and calling testexecute.exe I awlays get:
Cannot open "C:\Program files (x86)\smartbear\testexecute14\testexecute\bin\testexecute.exe" file because it is not a valid project suite or project file.
Wnen running from goold old cmd, everything is fine.
Did anyone knows what can be the cause?
Thank you...
Solved! Go to Solution.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Let's see your command line code please
Marsha_R
[Community Hero]
____
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Command line is:
C:\Program files (x86)\smartbear\testexecute 14\testexecute\bin\>.\testexecute.exe
Thank you
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Are initial dot and slash required ( '.\' ) ?
What if you type just testexecute.exe ?
/Alex [Community Hero]
____
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame
================================
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Alex,
The workaround is to use: Invoke-Item "TestExecute.exe"
But I would like to ask anyway why such strange behaviour.
Regards tcuser
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I see the same issue from powershell and command prompt. If I manually launch TestExecute.exe from the Bin directory, it works just fine.
If I do TestExecute.exe or .\TestExecute.exe, I get the errors like the original poster said. But, if I change it to lowercase: testexecute.exe, it works no issue.
I recently ran Windows updates on this machine (Windows 8.1), and am using TestExecute 14.10.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello. If you look at actual command line of launched process you will see:
"C:\PROGRA~2\SMARTB~1\TESTEX~2\Bin\TESTEX~1.EXE" "C:\Program Files (x86)\SmartBear\TestExecute 14\Bin\TestExecute.exe"
That's where source of the error lies -- PowerShell transfers full path to TestExecute.exe as the first command line argument of the created process.
Best way to launch some executable from PowerShell script is to use Start-Proccess cmdlet.
You may take a look at this usefull arcticle about launching processes form PowerShell:
https://social.technet.microsoft.com/wiki/contents/articles/7703.powershell-running-executables.aspx...
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the help, Vladimir!
@tcuser3, does it resolve the issue?
Tanya Yatskovskaya
SmartBear Community and Education Manager
