Content deleted Content added
m Cleaned up using AutoEd |
GreenC bot (talk | contribs) Rescued 1 archive link; reformat 1 link. Wayback Medic 2.5 per WP:USURPURL and JUDI batch #27aj |
||
(37 intermediate revisions by 28 users not shown) | |||
Line 1:
{{Short description|Tools for managing test automation}}
{{
'''Test automation management tools''' tools are specific tools providing test automation collaborative environment that is intended to make test automation efficient, clear for stakeholders and traceable. Since test automation is becoming cross-discipline (i.e. mixes both testing and development practices), the need of specific and dedicated environment for test automation is becoming vital.▼
{{Software development process}}
▲'''Test automation management tools'''
==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
* Organizing historical data.
==Compliance with Agile==
Test automation management tools
[[Test-driven development]] utilizes test automation as the primary driver to rapid and high-quality software production. Concepts of green line and thoughtful design are supported with tests before actual coding, assuming there are special tools to track and analyze within TDD process.
== 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 }}</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==
{{Reflist}}
{{DEFAULTSORT:Test Automation Management Tools}}
▲==See also==
[[Category:Automation software]]
[[Category:Software testing tools]]
[[Category:Collaborative software]]
|