I am looking into creating some PR build checks, and am wondering if anyone else has created something similar in the past.
We are using JSDoc type function headers, so the only task that I have so far is ensuring that doc generation is working on PR builds.
We had an issue where are bad .tcscript file was checked in, and broke references. I'm wondering if there is a way that I can check this before it gets committed to master.
The unique files for TestComplete (like tcScript and tcKDT) have a very different structure than most. While some attempts have been made in TC 14 to make merging such files easier, I still find that a manual comparison works best.
> [...] I still find that a manual comparison works best.
And I would like to add that your goal must be to avoid merging at all. Merging (and the constant risk of not identified merging errors) is the price that is paid for the development done by totally independent developers. In all other cases merging must be avoided. (Yes, I know that this is inconvenient and sounds not popular.)