The Case For PowerBuilder Unit Testing

    By: Mr. Yakov Werde on Apr 02, 2013

    As I advance through life, I think more and more about transferring assets to the next genera- tion. This thought is as pertinent in my professional career as PowerBuilder consultant as it is in my personal life. Many PowerBuilder systems have enjoyed what I term ‘reasonable longevity’. Some have been in production for over 15 years. You can well imagine that there these systems have provided a manifold return on investment to their stakeholders. Assuming the enterprise processes these systems support continue to remain relevant, it is reasonable to expect a new generation of developers will be needed to assume maintenance responsibilities. This being the case, the question “What kinds of actions can current developers take to assure the next generation developer efforts?” becomes extremely relevant. Or perhaps, I can restate the question as “There is so much complicated logic in the system. How can one be assured that a new developer, not familiar with all the business intricacies and platform nuances that embody a system, be able to continue the organization’s work without introducing serious flaws?”

    Login to read the article. Not a member? Create a free account!



     

     

    TwitterLLinkedinLFacebook

    Copyright © 2014 ISUG-TECH. All Rights Reserved
    All material, files, logos and trademarks within this site are copyright their respective organizations

    Terms of Service - Privacy Policy - Contact the Help Desk