The recent rise of Agile software development and the increased focus on shortening cycle times has put a spotlight on automated testing practices of all kinds. For traditional development teams the new emphasis on automated testing by developers has lead to a certain amount of confusion among both developers and QA professionals. Developers may wonder why they are now being asked to test when there is a separate testing department, and some software testers fear the developers writing tests may leave them disenfranchised. These concerns reflect a lack of understanding of the difference in purpose between the testing done by developers and the testing done by a quality assurance organization. Rather than posing a threat to external testing groups, developer testing offers them a tremendous opportunity to improve their effectiveness and efficiency, while at same time shedding the stigma of being the release bottleneck.