@Wlison wrote:
This program is already becoming difficult to maintain, and I am considering how to add unit test code to it.
This is what I was trying to point out as the challenge of building something large in-house, you need to put dedicated resources to maintain and sustain it over time, whereas going with COTS solutions, you save Engineering time and cost to maintain.
Now, if you use this framework to test something critical to your company's reputation, are you confident with data to back it?
Whenever faced with the question build or buy situation, I give the example of anyone can build something with enough resources (time, money, people) but is that what you want to do?
Of course, to save license cost for Microsoft Office365 or other applications, you may be asked to build in-house or even develop your own OS replacement to Microsoft to save that license cost, but factor in all the efforts involved and your expertise to focus on business problems.
