Content deleted Content added
InfinityBird (talk | contribs) m Grammar, punctuation, sentence structure, verb-noun agreement. Tag: gettingstarted edit |
Kfarnan421 (talk | contribs) copyediting Tag: gettingstarted edit |
||
Line 15:
==Compliance with Agile==
Test automation management tools are perfectly fit [[Agile]] methodologies and SDLC. In most cases, test automation covers continuous changes in order to minimize manual regression testing, therefore, at glance reporting is essential in order to be up to date and move the project quickly. The changes are usually noted by seeing differences 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 increases project quality attributes.
== TDD ==
[[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 ==
| |||