[[Test automation]] systems usually lackneed more reporting, analysis and meaningful information about project status. Test management systems target manual effort and do not give all the required information.<ref>{{cite book | last = Kartashov | first = Peter| title = Test Automation Management: A Call For Better Tools | url = http://www.automatedtestinginstitute.com/home/index.php?option=com_content&view=article&id=1276:ast-magazine&catid=105:ast-cover-description&Itemid=122 | year = 2011| publisher = Automated Software Testing Magazine}}</ref>
Test automation management systems leverage automation effortefforts towards efficient and continuous processes of delivering test execution and new working tests by:
* Making transparent, meaningful and traceable reporting for all project stakeholders.
* Easing test debugging through test results analysis workflow.
Line 17:
==Compliance with Agile==
Test automation management tools fit [[Agile software development|Agile]] Systems Development Life Cycle methodologies. In most cases, test automation covers continuous changes in order to minimize manual regression testing. Changes are usually noted by monitoring test log diffs. For example, differences in the number of failures signal probable changes either in AUT or in test code (broken test code base, instabilities) or in both. Quick notice of changes and unified workflow of results analysis reduces testing costs and increases project quality.
