STAREAST 2009 (Software Testing Analysis & Review)
4-8 May 2009
Agile Testing: Solving the Agilist's DilemmaRegister using the promo code SKES and save up to $300. Call the client support group at 888.268.8770 or register online at: https://www.sqe.com/STAREAST/Register/SelectConference.aspx
Wednesday May 6, 2009 1:45 p.m.
One problem with iterative software development is that teams are forced to write and test software incrementally—and repeatedly. Testers know that any change could break features in both obvious and hidden ways. Developers know that a change to their stable design is just around the corner. So, should we go back to designing software all up front and testing the whole product just before delivery? Of course not! So how do we solve this “Agilist’s Dilemma?” Rob Myers describes the two popular practices that can solve this dilemma: unit level test-driven development (TDD) and acceptance test-driven development (ATDD). Join Rob to explore the similarities and differences of these agile practices and learn how they support each other. Find out why ATDD is much more than traditional test-automation and how its practice drastically alters the role of the agile tester.
Better Software Conference & EXPO 2009
8-12 June 2009
Las Vegas, NV
Successful Teams Are TDD TeamsRegister using promo code SKBS and save up to $300. Call the client support group at 888.268.8770 or register online at: https://www.sqe.com/BetterSoftwareConf/Register/SelectConference.aspx
Thursday, June 11, 2009 12:45 p.m.
Test-Driven Development (TDD) is the practice of writing a test before writing code that implements the tested behavior, thus finding defects earlier. Rob Myers explains the two basic types of TDD: the original unit-level approach used mostly by developers, and the agile-inspired Acceptance-Test Driven Development (ATDD) which involves the entire team. Rob has experienced various difficulties in adopting TDD: developers who don’t spend a few extra moments to look for and clean up a new bit of code duplication; inexperienced coaches who confuse the developer-style TDD with the team ATDD; and waffling over the use of TDD, which limits its effectiveness. The resistance (overt or subtle) to these practices that can help developers’ succeed is deeply rooted in our brains and our cultures. Rob gives practical advice on overcoming that resistance and developing an “enjoyable development discipline” for a sustainable and practical TDD practice. With Rob’s practical advice, you may also discover how to lose weight and pay off your debts (seriously!). The success factors are identical.
I hope to see you there!