ContributionsMost RecentMost LikesSolutionsRe: Running Test Execute file from powershell These are the ps lines I use: $logpath = "C:\TestExecuteLogs\RunlogRegressie.mht" $testexecute = "C:\Program Files (x86)\SmartBear\TestExecute 11\Bin\TestExecute.exe" $p = Start-Process -filepath $testexecute -ArgumentList "`"C:\Regressie XL\RegressieTest\Regressie.pjs`"", /run, /exit, /SilentMode, /ExportLog:$logpath -verb runas -wait the -verb runas makes it run as administrator the -wait keeps the powershell session alive while testexecute is running You can lose these if you don't need them. Posting an error to the log containing a link? I am using a custom comparer when running my test. In order to post the correct results to the log I need to run my comparer, fetch the result, and in case of failure I have to execute files.compare in order to get messages to the log. This will give me 2 separate log-entries: an error (since I have specified this in de files.compare) which includes a picture for some reason, followed by a message with a link. Clicking on this link wil open my custom comparer with both files. What I would really like not to have to compare the files twice, and I would like to have only 1 log-entry for this. Also, I need to keep my logs small, so I would like to be able to keep the picture out of it. In order to achieve this it would be nice if I could: 1) Post a Log.Link with parameters so I could point it to my custom comparer and provide it with both files to be compared 2) Determine that my Log.Link should be an "Error" log-entry instead of an Log.Message 3) Determine that files.compare not add a picture to the log. 4) Integrate the files.compare Link line with the error line. log.SaveResultsAs(path,2) gives error I use log.SaveResultsAs (path, 2) in order to save the logresults to the local disk (so I can package and e-mail them). This has worked for years with testcomplete 7 and 9. Since we moved to testcomplete 11 I get the error "Can't save" in the log. This only seems to happen when the log contans an error or warning. Is this a known issue? Is there any way around it?