On Thu, Sep 15, 2016 at 8:07 AM, Benedict, Tom <[email protected]> wrote:
> Even upgrading to a newer version of 4D, which isn't refactoring, but > requires similar test coverage, is a major capital expense (>$100K not > including 4D licenses). > > What's the capital expense? > > So what do folks do to verify that their edits didn't break something? Do > you have automated tests? How do you ensure 100% coverage? And how do you > justify the costs? > I wish there was some sort of gui tester that worked. I've done two <=v12 -> v15 updates in the past year where there was a seemingly never ending dribble of form adjustments needed because fonts changed or lines disappeared. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
