The ‘M’ Word in Test Automation

    By: Mr. Brian J. Le Suer on Sep 02, 2013

    Maintenance is a dirty word in test automation circles, the ‘M’ word if you will. Test tool vendors don’t like to talk about it because it muddies the clear waters of record/playback and other ‘ease of use’ features that are often touted as silver bullets in the field of Software Quality Assurance. Test automation is supposed to reduce costs while increasing efficiency in a test organization, but test maintenance can quickly erode the return on investment if the approach and framework are not designed to ensure that tests can be modified quickly and easily as the target application changes over time. After all, if our applications were static, there would be no need for automated testing. When selecting tools and building an automation framework, there are at least four areas where making the right choices can significantly reduce maintenance costs: test plans, test tool architecture, test framework and test data.

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

    Released: September 2, 2013, 9:55 am | Updated: January 27, 2014, 6:12 pm
    Keywords: IT Strategy Article | Technical Journal | Brian Le Suer | IT Strategy | Test Automation




    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