Legacy test framework support

Imagine, you has joined the Company wich alredy practices test automation. Management is engaged on automation and ready to allocate resources for it; but the problems come from the other side.

Test code base is so huge, that adding new test case takes more and more efforts, and finally all test automation team resources go for support of existing test coverage.

In addition, tests are based on obsolete test tools and you can't replace it without ruining your existing code base.

In this speach I will talk about my experience of re-creation of the test framework for one of our applications from the scratch, and criteria whether it worth to do and how to do it without decreasing of test automation efficiency.