Test automation management tools: Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Revision as of 10:48, 21 October 2024 edit Citation bot (talk \| contribs) Bots 5,864,717 edits Altered isbn. Upgrade ISBN10 to 13. \| Use this bot. Report bugs. \| Suggested by Dominic3203 \| Category:Automation software \| #UCB_Category 31/57 ← Previous edit		Latest revision as of 06:17, 28 August 2025 edit undo InternetArchiveBot (talk \| contribs) Bots, Pending changes reviewers 5,677,638 edits Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5
(One intermediate revision by one other user 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-0 \| archive-date = 2012-04-25 \| access-date = 2011-03-01 \| archive-url = https://web.archive.org/web/20120425232401/http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470042125.html \| url-status = dead }}</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