Continuing our blog series on the challenges of traditional test automation, we come to realise that the applications we were test ten or twenty years ago are not the same anymore.
Today’s application complexity has increased fast, and test automation fails to uncover its full potentials because of limitations with existing automation tools and techniques, most of which originate from 30-year-old methodologies.
Software architectures have changed dramatically over time, and the use of modern technologies has also grown immensely. Most organisations are now shifting from mainframe systems and client/server and move towards cloud-native applications and microservices. System architectures are becoming more decentralized, evolving into a set of integrated systems that are becoming significantly more distributed.
Due to evolution into heterogeneous environments such as, software-as-a-service technologies, private clouds, public clouds, mobility, and the numerous integration points in between that keep it all working, testing has also grown in complexity.
It now needs to support multiple new applications built on disparate technologies. The interaction of these applications as well as the requirement to test them on different device configurations, add more challenges on testing teams. This means that, at any point testing teams need to be able to test APIs, regressions, the performance and UIs on various operating systems and devices.
Traditional outdated testing tools and processes do not support Agile and DevOps and were architected for months-long release schedules and simply don’t fit in the digital world, which requires immediate quality feedback with each new build.
Following the changes in the systems and architectures, the structure of the testing team has also moved from a highly centralized group responsible for all testing, to testing centers of excellence, to digital testing centers of excellence, to testers being embedded within Agile development team structures.
Software architectures have changed dramatically over time, and the use of modern technologies has also grown immensely. Most organisations are now shifting from mainframe systems and client/server and move towards cloud-native applications and microservices. System architectures are becoming more decentralized, evolving into a set of integrated systems that are becoming significantly more distributed.
Due to evolution into heterogeneous environments such as, software-as-a-service technologies, private clouds, public clouds, mobility, and the numerous integration points in between that keep it all working, testing has also grown in complexity.
It now needs to support multiple new applications built on disparate technologies. The interaction of these applications as well as the requirement to test them on different device configurations, add more challenges on testing teams. This means that, at any point testing teams need to be able to test APIs, regressions, the performance and UIs on various operating systems and devices.
Traditional outdated testing tools and processes do not support Agile and DevOps and were architected for months-long release schedules and simply don’t fit in the digital world, which requires immediate quality feedback with each new build.
Following the changes in the systems and architectures, the structure of the testing team has also moved from a highly centralized group responsible for all testing, to testing centers of excellence, to digital testing centers of excellence, to testers being embedded within Agile development team structures.
Tagged under