Forum Discussion
Chris_Moesel
17 years agoOccasional Contributor
I think that many of the diff tools support command-line options to start them. WinMerge has it's command line instructions here:
http://winmerge.org/2.6/manual/CommandLine.html
One of the preference settings for SOAPui could be the path to your WinMerge executable. When user wants to diff the failed test, you would save the expected and actual responses as separate files in a temp directory and then launch WinMerge using the command line call.
Of course, WinMerge only works on Win32 systems, so you might want to support a few others as well...
OR you could make it completely generic. The preferences could accept the path to any diff tool, along with the needed arguments, and you could use placeholders for the expected and actual responses.
For example, WinMerge configuration might look like this:
Executable: C:\Program Files\WinMerge\WinMerge.exe
Args: /ub /dl "Expected Response" /dr "Actual Response" ${Expected} ${Actual}
That requires a bit more of a power user, but it's super flexible. Anyway, if I write much more then I'll start wondering if I should have just coded it myself and made a contribution... So I'll stop here.
http://winmerge.org/2.6/manual/CommandLine.html
One of the preference settings for SOAPui could be the path to your WinMerge executable. When user wants to diff the failed test, you would save the expected and actual responses as separate files in a temp directory and then launch WinMerge using the command line call.
Of course, WinMerge only works on Win32 systems, so you might want to support a few others as well...
OR you could make it completely generic. The preferences could accept the path to any diff tool, along with the needed arguments, and you could use placeholders for the expected and actual responses.
For example, WinMerge configuration might look like this:
Executable: C:\Program Files\WinMerge\WinMerge.exe
Args: /ub /dl "Expected Response" /dr "Actual Response" ${Expected} ${Actual}
That requires a bit more of a power user, but it's super flexible. Anyway, if I write much more then I'll start wondering if I should have just coded it myself and made a contribution... So I'll stop here.