Editing Software testing (section)

=== Continuous testing ===
{{Main|Continuous testing}}

Continuous testing is the process of executing [[test automation|automated tests]] as part of the software delivery pipeline to obtain immediate feedback on the business risks associated with a software release candidate.<ref name="essential">{{Cite web |last=Auerbach |first=Adam |date=August 3, 2015 |title=Part of the Pipeline: Why Continuous Testing Is Essential |url=https://www.techwell.com/techwell-insights/2015/08/part-pipeline-why-continuous-testing-essential |access-date=January 12, 2018 |website=TechWell Insights |publisher=TechWell Corp.}}</ref><ref name="stickym">{{Cite web |last=Philipp-Edmonds |first=Cameron |date=December 5, 2014 |title=The Relationship between Risk and Continuous Testing: An Interview with Wayne Ariola |url=http://www.stickyminds.com/interview/relationship-between-risk-and-continuous-testing-interview-wayne-ariola |access-date=January 16, 2018 |website=Stickyminds}}</ref> Continuous testing includes the validation of both [[functional requirements]] and [[non-functional requirements]]; the scope of testing extends from validating bottom-up requirements or user stories to assessing the system requirements associated with overarching business goals.<ref name="pnsqc">{{Cite conference |last1=Ariola |first1=Wayne |last2=Dunlop |first2=Cynthia |date=October 2015 |title=DevOps: Are You Pushing Bugs to Clients Faster? |url=http://uploads.pnsqc.org/2015/papers/t-007_Ariola_paper.pdf |conference=Pacific Northwest Software Quality Conference |access-date=January 16, 2018}}</ref><ref name="shift">{{Cite web |last=Auerbach |first=Adam |date=October 2, 2014 |title=Shift Left and Put Quality First |url=https://www.techwell.com/techwell-insights/2014/10/shift-left-and-put-quality-first |access-date=January 16, 2018 |website=TechWell Insights |publisher=TechWell Corp.}}</ref>