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.