Content deleted Content added
→API testing: Added hyperlink for "single-responsibility principle". |
Added more factors to consider when considering implementation of test automation Tags: Reverted Visual edit |
||
Line 48:
===Factors to consider for the decision to implement test automation ===
What to automate, when to automate, or even whether one really needs automation are crucial decisions which the testing (or development) team must make.<ref>
{{cite web|url=http://www.stickyminds.com/sitewide.asp?Function=edetail&ObjectType=ART&ObjectId=2010|title=When Should a Test Be Automated?|author=Brian Marick|publisher=StickyMinds.com|access-date=2009-08-20}}</ref> A multi-vocal literature review of 52 practitioner and 26 academic sources found that five main factors to consider in test automation decision are: 1) System Under Test (SUT), 2) the types and numbers of tests, 3) test-tool, 4) human and organizational topics, and 5) cross-cutting factors. The most frequent individual factors identified in the study were: need for regression testing, economic factors, and maturity of SUT.<ref>{{Cite journal|last1=Garousi|first1=Vahid|last2=Mäntylä|first2=Mika V.|date=2016-08-01|title=When and what to automate in software testing? A multi-vocal literature review|journal=Information and Software Technology|volume=76|pages=92–117|doi=10.1016/j.infsof.2016.04.015}}</ref> Costs involved with test automation, deadlines to meet, and the returns on investment are other important considerations to factor in when deciding to implement test automation.<ref>{{Cite web |title=Is Test Automation the Right Strategy for Your Business? - My Blog |url=https://www.cloudesign.com/blogs/is-test-automation-the-right-strategy-for-your-business/ |access-date=2024-09-20 |website=www.cloudesign.com}}</ref>
===Plateau effect===
| |||