The book Evolutionary architecture talks about how software architecture needs to keep evolving with the changes to business priorities and the tech landscape changes, with fitness functions guiding the evolution. The same concept shall and should be applied to the software testing strategy which is what I coin as Evolutionary testing strategy.
Evolving the test strategy is indeed inevitable and has led to downfall when not adopted in many cases. Keeping the test strategy unpolished is like keeping one wheel in a tricycle constant while the other two (the business requirements and the software architecture) keeps moving! Even though it may sound obvious, for some reason, there has never been proper processes, roles or responsibilities defined to evolve the testing strategy. This talk delves into the problems of not evolving the testing strategy and guide through a few helpful steps into implement the practice of continuously evolving the testing strategy.
Video producer: https://oredev.org/
This article provides an excellent overview of essential software testing practices. I especially appreciate the emphasis on integrating testing early and the benefits of automation. For further reading and resources on software testing, be sure to check out Software Testing Board. Thanks for the valuable insights