P2P

60 P E E R T O P E E R : I L T A ' S Q U A R T E R L Y M A G A Z I N E | S U M M E R 2 0 2 1 • Triaging defects from failed automation tests. • PM, IT all need onboarding Environments • Your environments need to start by meeting your current manual testing needs. • Load and performance, can it handle increased load of automated tests. • Availability – dedicate availability of environment(s). • Application Stability – are the environments stable enough for automated tasks. • Data – watch for insufficient data variance and/or cleansing. Alignment with teams • Aligning with your desktop apps team and your development team on process and storage of source code, packaging and deployment practices. Maintenance • This is an ongoing activity, as long as there are changes to the app or environment is modified, automated tests are sensitive to change that are not visible to a manual tester but make automated test fail. • Who maintains the tests, handover to Business as Usual team. Trust • Is there trust in the current manual testing results. • Demonstrating test automation trust is important by duplicating results from manual tests or by showing the automated tests found different defects. • It's all about setting expectations – all doesn't come immediately, it must be well managed. Lastly Once you've balanced those costs and benefits, it can come down to where you are in your quality journey and how much you want or are able to invest in tools and hardware, upskilling or hiring staff with automation skills, and maintaining the automated tests. If you need any help in working through this evaluation or developing a test automation strategy, I can help, just let me know. ILTA A S K I N G T H E R I G H T Q U E S T I O N S

• Cover