2013:how_to_narrow_down_what_to_test
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 2013:how_to_narrow_down_what_to_test [2013/01/08 05:53] – jonjagger | 2013:how_to_narrow_down_what_to_test [2016/06/11 14:05] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 11: | Line 11: | ||
| 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.\\ | 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.\\ | ||
| \\ | \\ | ||
| - | More Information about the talk: | + | Jon: Zsolt added the following which was not intended to be part of the proposal: |
| - | This talk has already been given at Agile Cambridge 2012 where the infoq recording was done, and the presented slides are available here: https:// | + | |
| \\ | \\ | ||
| Roger: Yes (do we have any feedback from anyone who attended Agile Cambridge?) | Roger: Yes (do we have any feedback from anyone who attended Agile Cambridge?) | ||
2013/how_to_narrow_down_what_to_test.1357624398.txt.gz · Last modified: 2016/06/11 14:05 (external edit)