Be the first to like this
If you have an established product which came about before the widespread use of the unit and system testing, then you know the problem.
The old code cannot be made testable without a significant effort of throwing it away and writing it anew.
What does it mean for the QA? It means endless repetitions of manual test runs. Sounds like fun? Yeah.. Nah!
In this presentation you will find two ways to make legacy applications testable through automation: an easy one, and a good one. The main benefit they provide is a basis for the further refactoring of the application, without damaging it.
Think of it as a Catch-22: you can't make your old app code testable without severely changing it, and you can't be sure that your changes work because you have no tests to verify them.
If you are a QA and you work with older apps and systems doing a lot of manual testing, then this is the topic for you.
This talk was given at ITx 2016 in Wellington, New Zealand, for Testing Professionals Network.