Page - 111 - in The Future of Software Quality Assurance

TestingStrategies inan AgileContext ZornitsaNikolova Abstract Testing in an Agile context is extremely important, not only with its function to ensure quality but also to guide development efforts into the right direction.This is relatedtoashift in testingparadigms,withqualitybeingviewedas afactorearlyoninproductdevelopment,rather thana late-stagereactiveactivity. It also requires the application of different approaches, such as automation, to enable the flow of potentially shippable product increments. Many teams find themselves stuck into the old ways of testing, especially as they work on legacy systems. However, investment in upskilling quality experts, applying the proper tools, and changing the way testing is done can bring tremendous value and opportunities for innovation. Proper change management needs to be applied to enable teams transitionsuccessfully intoanAgilemindsetandnewpractices. Keywords Software testing · Softwarequality · Agile testing · Test automation 1 Introduction Irrespective of the methodology that you use for managing your product develop- ment, quality assurance is important. And when we say “quality assurance,” we typically mean “testing.” Agile contexts are not different in this sense. In Agile, we value “working product more than comprehensive documentation,”1 hence the majority of teams’ efforts shall be focused on creating software and makingsure it doeswhat it is supposed todo. Yet, inmanycaseswhenwelookatprocessesinvariousteams,evenif theyclaim they are Agile, we still see quality as just the final step of creating the product.We design, we build, and then we test, usually with a focus on discoveringbugs. Even though we talk about team ownership on results, it’s still a quality expert mainly 1Manifesto for AgileSoftware Development, www.agilemanifesto.org Z.Nikolova Leanify, Sofia, Bulgaria ©The Author(s) 2020 S.Goericke (ed.), The Future of Software QualityAssurance, https://doi.org/10.1007/978-3-030-29509-7_9 111