I am looking for a sane way to organize our test scenarios and test plans. We have a quite modular application, which is customized for each customer. What else, each customer has several mutations of the application.
For example, imagine a calculator, scientific calculator, programmable calculator and each of those in different languages or numerical systems.
Right now, we have a separate test plan and list of scenarios for each customer-product combination. But the maintenance is a pain, because each time a feature gets changed, that is present in more products, we have to update several files. However, even some of the core features of the product, which are completely same for 9 customers are behaving differently for another.
What I think, we are missing, is some central document, which would describe all features together and from which we would then generate the test execution plan.
But I am not sure how to structure such a document, how to describe the "common features" and "custom specials" so these are maintainable.
Is there anyone who has used something similar or solved similar problems?