13

In addition to reading Working Effectively with Legacy Code, I have a few recommendations from experience: Since there is little to no documentation, tour the software. Go through the software using it as if you were a user, noting what it does and what you can find about why it works the way it does. Talk to long-time users. Since this is internal software,...


4

Reference material- Working Effectively with Legacy Code by Michael Feathers The books discusses working with legacy systems, not just testing them. Some of the suggestions are using a module's Logical complexity, Dependency level and Priority to decide on what to test. It then suggests two approaches as to what to start with- easy first or hard first, both ...


1

You can use the Heuristic Test Strategy Model as a starting point to design your approach for testing (a mindmap version can be found here). By laying out the Project Environment, you will realize the boundaries and limitations of the project. Product Elements will help you to understand the components of the product, which you can then do risk analysis and ...


Only top voted, non community-wiki answers of a minimum length are eligible