Page - 117 - in The Future of Software Quality Assurance

Testing Strategies in an AgileContext 117 maintain and update. Therefore, we shall spend most effort on the lower layers, automating on a unit and service level, while still doing manual testing on the UI layer. Note, however, that we can optimize manual testing strategies as well to get thebiggestvalueof theeffort spent there.Coming to themanualUI-basedtests, we don’tneed to do full-blownregression testing, or coverall end-to-endscenarios, as wehavealreadycoveredthemonthe integrationtests layer.Here, the focus ismore onnonfunctional(performance,security,usability,accessibility,etc.) testing,aswell as simulationof real-lifeusage throughexploratoryanduseracceptance testing. To summarize, major investment in automation makes sense for products that are still in growth and innovationmode, and it is required for a long-term success. We shall also be selective on the amount of investment per system layer to gain maximumreturns—investinginautomationofunit and integration tests is typically advisable, as it speeds up development. When it comes to UI testing, we might consider automating some of the manually done smoke and regression tests, while taking into account the ongoing test maintenance effort and picking appropriate tools. 4 TransitioningtoAgileTesting Even when the team and the organization is convinced in the benefits of Agile testing, including investment in test automation, getting started on it might be anotherhardtask.Therearealotofchallengestochangingtheentireprocessofhow you plan and execute tests—from purely infrastructural (tools, test system design, etc.) throughskills in the team to create andexecute those tests to mindset changes that need to happen, and fears that need to be overcome. Starting from point zero is scary and not easy at all, and many teams might find themselves at a loss as to where theyshouldstart. I am a strong believer in goal-oriented thinking, and systems such as OKR (Objectives and Key Results). Starting with the end goal in mind creates focus, motivation, and resourcefulness in people to overcome challenges as they go. So, defining our short- and midterm objectives is an excellent way to kick off a transformation of quality assurance in the organization. Of course, as in any goal-setting process, being unrealistically ambitious might fire back at some point, creatingasenseofdisbeliefanddemotivationin theteam.Wehavetochoosetargets carefully, ideally incollaborationwith the team. A good practice that I have experienced personally might be to get a team of earlyadoptersonboard, train them,andget themsupport fromanAgilecoachwith knowhowinAgiletestingparadigms.This teambecomesthecatalystforsubsequent activities within the individual Agile teams as well. Note that you can have the ScrumMasterscoachingteamsinAgile testingpractices,but if theScrumMaster is notatechnicalperson,heorshemightnotbethemostappropriateonetoassumethis role.At thispoint, themost important thingwouldbe that theperson is enthusiastic to learn and work to implement and improve these practices within the team. Once