Test automation management tools: Difference between revisions

Revision as of 22:30, 28 February 2011

Revision as of 00:32, 1 March 2011

Line 1:

{{unreferenced|date=February 2011}}

'''Test automation management tools''' tools are specific tools providing test automation [[Collaborative software|collaborative]] environment that is intended to make [[Test automation|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.

==Motivation==

[[Test automation]] usually lacks of reporting, analysis and providing meaningful information about project status from automation perspective. Test management systems from the other hand mostly targeted on manual effort and cannot give all the required information.

Test automation management system leverages automation effort towards efficient and continuous process of delivering test execution and new working tests by:

-* Making transparent, meaningful and traceable reporting for all project stakeholders

-* Easing test debugging through built-in test results analysis workflow

-* Providing valuable metrics and KPIs – both technical and business-wise (trend analysis, benchmarking, gap analysis, root cause analysis, risk point analysis)

-* Grid benchmarking and comparison of test execution days reduces analysis and review effort

-* Clean traceability with other testing artifacts (test cases, data, issues, etc)

-* Keeping historical data in a single place, easily retrievable

-* Post project analysis and automation performance assessment (basically progress of test coverage shows the group performance)

==Compliance with Agile==

Test automation management tools are perfectly fit [[Agile]] methodologies and SDLC. In most cases test automation is to cover continuous changes in order to minimize manual regression testing, therefore at glance reporting is essential to be up to date and move project quickly. The changes are usually noted by seeing difference of errors in test logs between day A and day A+1. For example, difference in number of failures (logs errors) signal about probable changes either in AUT or in test code (broken test code base, instabilities) or rarely in both. Quick notice of changes and unified workflow of results analysis, ultimately, reduces cost of testing overall and moreover increase confidence on project quality attributes with clean reporting on hand.

== TDD ==

[[Test-driven development]] utilizes test automation as primary driver to rapid and high-quality software production. Concepts of green line and thoughtful design supported with test before actual coding assume having special tools to track, analyze and make right decision within TDD process.

== Continuous Integration ==

Another proper test automation practice is being part of [[Continuous integration|continuous integration]] which explicitly supposes to have automated test suites as final stage upon building, deployment and distributing new version of software. Basically, based on acceptance test results, a build is declared either as qualified for further testing or not qualified (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

}}</ref> CI web dashboards provide all relevant information on all stages of software building including automation test results. However, CI dashboard does not support comprehensive operations and views for automation engineer. This is another reason for having dedicated management tool which can supply high-level data to other project management tools such as CI, [[Test management tools|test management tools]], [[Issue management|issue management]], [[Change management (engineering)|change management]].

==References==

{{Reflist}}

==See also==

* [http://en.wikipedia.org/wiki/Test_management[Test management|Test management]]

* [[Test automation|Test automation]]

* [http://en.wikipedia.org/wiki/Test_automation automation]

* [http://en.wikipedia.org/wiki/Test_management_tools[Test management|Test management tools]]

* [http://gredy.net Gredy - the only test automation management tool]