SRT Solutions http://srtsolutions.com 2701 http://www.linkedin.com/in/dburton Ann Arbor, MI Dennis Burton http://developusing.net 4.65 /avatars/2701/thumb/headshot.JPG 2009-05-20T17:21:42+00:00 131 1118 Now that you have decided to integrate testing into your development process, you find that when one test breaks, it seems like they all break. You also find that with so many tests broken, identifying the source of failed tests is challenging. Another challenge is that occasionally, tests are just plain hard to write. In this session we will discuss patterns and techniques for writing tests that are more robust and provide better information. This includes techniques that you can apply to your design when writing new code to make testing easier, as well as tools for working with existing applications that do not have good test coverage. 2009-06-13T15:23:20+00:00 2009-06-26T16:00:01+00:00 4.65 2009-06-28T14:42:33+00:00 110 1229 Now that you have decided to integrate testing into your development process, you find that when one test breaks, it seems like they all break. You also find that with so many tests broken, identifying the source of failed tests is challenging. Another challenge is that occasionally, tests are just plain hard to write. In this session we will discuss patterns and techniques for writing tests that are more robust and provide better information. This includes techniques that you can apply to your design when writing new code to make testing easier, as well as tools for working with existing applications that do not have good test coverage. http://www.indycodecamp.com/Sessions/tabid/554/Default.aspx 2009-06-28T14:42:33+00:00 2009-05-16T16:00:01+00:00 2009-06-28T14:45:27+00:00 1230 Now that you have decided to integrate testing into your development process, you find that when one test breaks, it seems like they all break. You also find that with so many tests broken, identifying the source of failed tests is challenging. Another challenge is that occasionally, tests are just plain hard to write. In this session we will discuss patterns and techniques for writing tests that are more robust and provide better information. This includes techniques that you can apply to your design when writing new code to make testing easier, as well as tools for working with existing applications that do not have good test coverage. HCR Manorcare building 53 http://www.nwnug.com/graffiti/meetings/dennis-burton-test-driven-is-driving-me-insane/ 2009-06-29T13:02:22+00:00 2009-04-21T18:30:01+00:00 2009-06-28T14:38:30+00:00 1227 Now that you have decided to integrate testing into your development process, you find that when one test breaks, it seems like they all break. You also find that with so many tests broken, identifying the source of failed tests is challenging. Another challenge is that occasionally, tests are just plain hard to write. In this session we will discuss patterns and techniques for writing tests that are more robust and provide better information. This includes techniques that you can apply to your design when writing new code to make testing easier, as well as tools for working with existing applications that do not have good test coverage. 1260 Anthony Hall, MSU 51 http://glugnet.org/Events/tabid/1364/ctl/ViewDetail/Mid/3505/ItemID/142/d/20090416/Default.aspx?SkinSrc=[L]Skins%2fDNNspot-Halite%2fblue 2009-06-28T14:38:30+00:00 2009-04-16T18:30:01+00:00 2009-06-28T14:48:06+00:00 1231 Now that you have decided to integrate testing into your development process, you find that when one test breaks, it seems like they all break. You also find that with so many tests broken, identifying the source of failed tests is challenging. Another challenge is that occasionally, tests are just plain hard to write. In this session we will discuss patterns and techniques for writing tests that are more robust and provide better information. This includes techniques that you can apply to your design when writing new code to make testing easier, as well as tools for working with existing applications that do not have good test coverage. Microsoft Offices, 1000 Town Center Dr., Suite 1930, Southfield, MI 49 http://migang.org/MeetingInfo.aspx?CntProv=Events&CntItem=918abb85-b6f6-4208-a6f5-4340db63d2b3&ReturnURL=%2fMeetings.aspx&CntCatID=ab51a0eb-da64-4a1b-b16b-413d7ca4cf62 2009-06-28T14:51:33+00:00 2009-03-18T18:30:01+00:00 2009-06-28T14:40:43+00:00 1228 Now that you have decided to integrate testing into your development process, you find that when one test breaks, it seems like they all break. You also find that with so many tests broken, identifying the source of failed tests is challenging. Another challenge is that occasionally, tests are just plain hard to write. In this session we will discuss patterns and techniques for writing tests that are more robust and provide better information. This includes techniques that you can apply to your design when writing new code to make testing easier, as well as tools for working with existing applications that do not have good test coverage. New Horizons Flint 52 http://glugnet.org/Events/tabid/1364/ctl/ViewDetail/Mid/3505/ItemID/158/d/20090312/Default.aspx?SkinSrc=[L]Skins%2fDNNspot-Halite%2fblue 2009-06-28T14:40:43+00:00 2009-03-12T18:30:01+00:00 2009-06-28T14:57:57+00:00 1232 abstract needed New Horizons Flint 52 http://developusing.net/2008/03/28/SpeakingOnPowerShell.aspx http://glugnet.org 2009-06-28T14:58:41+00:00 2008-04-10T18:30:01+00:00