Automated testing in a product company: handling tons of features and versions in production
If you work on a quite complex product and there's a bunch of versions you have to support, there will appear a pack of problems that impact on QA work critically. Each interface must be tested with its own tooling, keeping in mind the distinctions between versions and capability of scaling the testing depending on available resources. And that's just a beginning of the list!
I will tell on how we chose our solution for organising the AQA process in GridGain with pros and cons and why we chose in a multiversional framework.