XP 2013 - How to Narrow Down What to Test

Nowadays testing legacy code, especially writing automatic test cases costs a lot. This looks like an extra expense in the short run, but saves a lot of trouble in the long run. However, not every organisation can afford to spend expensive coding time on testing that is considered having as no real value to the customer. Especially when we are talking about a large piece of untested legacy code.

The best way to do this effectively is to test those parts of the code that really need to be tested. In my presentation I’m going to share several methods that can be used to find areas that are worth testing so that organizations do not have to spend more effort on testing legacy code than what is absolutely necessary.

comments powered by Disqus