"Files diff utility" how does it work? Example?

Yes!  Now we're getting somewhere. 

Which Beyond Compare executable did you specify in the "Diff name" field?  Beyond Compare has at least three of them (e.g. BComp.exe and BCompare.exe).  Also, did you leave default arguments in the "Command line" field?

I'm still unclear on if/how this will work with TestExecute.  Are these settings saved in the project or project suite?  The nature of the UI makes it look like they are application settings rather than file settings. If it won't work with TestExecute then I may not be able to use it.

Many thanks, John

Hi, thanks for the response.

Yes, that's the reference I found as well.  As you can see there are no examples.  When you call an external comparison tool like Beyond Compare from the command line it returns a value reflecting the results of the comparison.  WinDiff (as old as the hills and not support in Windows 11) and PowerShell's Compare-Object do the same thing. My expectation is that result is subsequently reflected in the TestComplete log as a pass or fail.  Unfortunately, that's not happening.

If all it does is run the comparison in Beyond Compare and then force me to review an output file from Beyond Compare there is no value in that.  I can just call Beyond Compare directly from a script and accomplish that task.

The feature implies you can use Beyond Compare as the comparison tool and then get the results back in TestComplete.  There is value in that because Beyond Compare is content aware and can thus use a more appropriate comparison routine (e.g. it will recognize a CSV file and compare the contents of the CSV) to evaluate the files.  

The Files.Compare method in TestComplete does a binary comparison only.  That is very fragile since subtle formatting changes unrated to the values contained in the CSV will cause a false positive.

Just for reference below is the VBScript code I use with the file comparisons.  It's not working when I try to use the external comparison tool functionality.  It does work when I use the default settings but I get false positives for failures as I previously described.

If Files.Compare(aFile.Path, s_ResFilePath & aFile.Name, 0, False) Then
          Log.message "Pass: The files matched: " & aFile.Name,
    	  Call aqFile.Delete(aFile.Path) 'Delete the file if the comparison succeeded
        Else
          Log.Warning "Fail: The files did not match: " & aFile.Name
 End If

Thanks for giving it a try in TestExecute.  I don't think I'll have the same security issues but I'll find out.

Additionally, I'm not sure I agree with your assessment that my prior responses were narcissistic.  I'm confident Marsha had good intentions but in this case it seems she did not have the domain knowledge assist me.  

Directing me to the documentation was simply unhelpful.  That is not a personal attack, but simply a statement of fact.  As noted in my original post, I had already reviewed the documentation and found it lacking.

I didn't like the tone of the below responses directed against a fellow member (me).  However, if you want to portray me as "the bad guy" I'll accept that.  I can be direct, there is no doubt about that.  I can also be appreciative as you saw in my responses to you.

Like I said, the examples are given in the documentation for each of the comparisons.

you have no idea what I know about TestComplete or don't