Quality Assurance (QA)

>>>Quality Assurance (QA)
Quality Assurance (QA) 2017-12-07T07:54:53+00:00

The path to quality is changing

Brands that recognize the importance of digital engagement are investing more of their budgets into ensuring the high quality of their mobile apps. According to a new report from Capgemini, quality assurance and testing now make up 35% of corporate IT spending, and by 2018, researchers predict that 40% of yearly IT allocations would go to those same two areas. And when it comes to prioritizing, Capgemini found that mobile apps and delivering seamless digital experiences are the main focus areas of executives today.

This shouldn’t come as any surprise to digital marketers, business leaders and mobile app developers, as you’ve all seen what can go wrong when mobile app testing and continuous quality are put on the sidelines. So many environmental factors and user conditions can impact the user experience, and once that mobile app is closed after a bad experience, consumers aren’t likely to open it back up. So, in order to stay on the top charts and get high app store ratings, brands have fine-tuned their mobile app testing strategies.

  • How software quality is performed is changing
    • There’s no one universal QA model anymore
  • Customer facing apps are changing the fastest
    • Forrester categorizes these as systems of engagement
    • Web & mobile are the leading “platforms” and IoT is growing fast
    • Engagement driven from sensors is evolving engagement, think Alexa or connected car or chat bots
      • Perfecto refers to these as next gen digital engagement methods
  • The push to deliver innovation faster is transforming software QA
    • Shrinking release cycles is what makes manual testing ‘unacceptable’ forcing the adoption of automation
      • The two extremes of QA – 1) separate QA professionals sitting within a TCOE, 2) testing is the responsibility of the feature team with either a dedicated test engineer or a distributed responsibility across developers.
      • Earlier, QA professionals had deep business process knowledge providing them insight regarding primary flows and edge cases
      • Automation creates new skill set expectations, either learn how or find yourself at risk
        • Commercial tools that supported scripting methods are giving way to open source tools supporting programing languages used by developers. AI based approach will be third technical wave washing over QA
        • Frequently, to support multiple feature teams, the role of the TCOE is evolving from a service provider to an enabling team focused on sustaining test automation frameworks and developing reusable components (e.g., authentication) to enable feature teams to increasingly focus on coding tests for new features.
      • Velocity has also driven the adoption of agile methodologies and DevOps
    • Combined they change the expectations how teams behave and who is responsible for quality
      • Traditional QA roles are being redefined to be devtesters, test engineers or simply developers who test (SDET)
      •  Google’s approach to software testing illustrates how high velocity teams are evolving how testing is executed
    • What once was a separate phase occurring late in the development cycle in now executed continuously as software is built
    • DevOps adoption is also expanding the scope of testing – not only continuously during pre-prod but also during phased deployment to prod and inclusive of ongoing testing in prod