Content deleted Content added
No edit summary |
No edit summary |
||
Line 27:
|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]], [[issue management]], [[Change management (engineering)|change management]].
== Continuous Automation ==
Continuous Automation is a subset of CI which can be considered as part of CI or as independent workflow. Different companies and project have different vision and place of automation. In general this isolated from development approach is typical for functional testing and QA teams and teams which are doing independent software verification which could not rely on development codebase and infrastructure (e.g. outsourcing, UAT, etc.)
The Common workflow in test automation can be decomposed as follows:
# Develop, debug and setup tests on production run - test shipping
# Regular Running ready-to-go tests
# Perform test results analysis and maintenance that results in:
* Revealing project (AUT) defects: if new one - report the issue, if persisting one - get confidence that it is covered
* Finding out problems in testing code - to Debug
# Prepare report and notify stakeholders about analysis completion
==References==
{{Reflist}}
[http://www.slideshare.net/adgredy/continuous-automation?from=ss_embed Slideshare presentation about continuous automation]
==See also==
Line 35 ⟶ 47:
* [[Test automation]]
* [[Test management|Test management tools]]
[http://gredy.net/ Test automation management tool Gredy]
{{DEFAULTSORT:Test Automation Management Tools}}
| |||