Back to [[conference:committee:proposals-2013]]\\
\\
**Title**: How to Narrow Down What to Test\\
**Proposer**: [[2013:zsolt_fabok]]\\
**Type**: Tutorial\\
**Duration**: 45 minutes\\
**Description**: \\
Nowadays testing, especially writing automatic test cases, costs a lot. This looks like an extra expense in short time, but saves a lot of trouble in the long run. However, not every organisation can afford to spend expensive coding time on testing that considered as no real value to the customer.\\
\\
The best way to do this is to be effective, so test those parts of the code which really need to be tested. In my presentation I'm going to share several methods that can be used to find areas which are worth testing so that organizations do not have to spend more effort on testing than what is absolutely necessary. These methods will be presented on java and ruby on rails examples.\\
\\
Jon: Zsolt added the following which was not intended to be part of the proposal: More Information about the talk: This talk has already been given at Agile Cambridge 2012 where the infoq recording was done, and the presented slides are available here: https://speakerdeck.com/u/fabokzs/p/narrow-down-what-to-test\\
\\
Roger: Yes (do we have any feedback from anyone who attended Agile Cambridge?)