Test automation management tools: Difference between revisions

Revision as of 10:49, 3 July 2023

Latest revision as of 23:45, 4 May 2025

(2 intermediate revisions by 2 users not shown)

Line 5:

==Motivation==

[[Test automation]] systems usually need 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 | archive-url = https://web.archive.org/web/20100615024956/http://www.automatedtestinginstitute.com/home/index.php?option=com_content&view=article&id=1276:ast-magazine&catid=105:ast-cover-description&Itemid=122 | url-status = usurped | archive-date = June 15, 2010 | year = 2011| publisher = Automated Software Testing Magazine}}</ref>

Test automation management systems leverage automation efforts towards efficient and continuous processes of delivering test execution and new working tests by:

Line 23:

== Continuous Integration ==

Another test automation practice<ref>{{cite book | last = Kolawa | first = Adam |author2=Huizinga, Dorota | title = Automated Defect Prevention: Best Practices in Software Management | url = http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470042125.html | year = 2007 | publisher = Wiley-IEEE Computer Society Press | isbn = 978-0-470-04212-50 }}</ref> is [[continuous integration]], which explicitly supposes automated test suites as a final stage upon building, deployment and distributing new versions of software. Based on acceptance of test results, a build is declared either as qualified for further testing or rejected.<ref name="Fowler, Continuous Integration practices" >{{Cite web

|url=http://martinfowler.com/articles/continuousIntegration.html#PracticesOfContinuousIntegration

|title=Continuous Integration

|accessdate=2009-11-11

|last=Fowler |first=Martin |authorlink=Martin Fowler (software engineer)

}}</ref> Dashboards provide relevant information on all stages of software development including test results. However, dashboards do not support comprehensive operations and views for an automation engineer. This is another reason for dedicated management tools that can supply high-level data to other project management tools such as [[test management]], [[issue management]] and [[Change management (engineering)|change management]].

==References==