W17 Concurrent Session Wednesday 06/11/2008 2:45 PM – 4:15 PM Agile Software Testing Strategies Agile Software Testing Strategies Presented by: Jared Richardson 6 th Sense Analytics Presented at: Better Software Conference & EXPO June 9 – 12 2008: Las Vegas, NV, USA 330 Corporate Way, Suite 300, Orange Park, FL 32043 888-268-8770 � 904-278-0524 � sqeinfo@sqe.com � www.sqe.com
Jared Richardson Jared Richardson , co-author of Ship It! A Practical Guide to Successful Software Projects , is a regular conference speaker and an agile coach at 6th Sense Analytics. Jared has been in the industry for more than fifteen years as a consultant, developer, tester, and manager. Until recently, he was an independent consultant focused on helping teams build better software. He's now bringing that same focus to 6th Sense Analytics and its clients, using both the 6th Sense toolset and his unique perspective. Jared can be found online at www.AgileArtisans.com and www.6sa.com/blog.
Agile Software Testing Strategies By Jared Richardson http://AgileArtisans.com
Test Strategy Successful Agile • Strategy • Team
Prerequisites • Continuous Integration • Test Automation
Automated Tests Rust Code Breaks Sync Fails Trust Fails
Two Scenarios • Fix 1 to 3 tests • Fix 800 tests
Your Code
Public API Supporting Classes
Focused Tests
Tests Broad
Unit Tests • Exercise one unit • No external resources • Fast • Focused • Labor intensive
Mock Client Test • A system or module • Integration test • Broad • Slow
Tests Require • Continuous Integration • Frequent check-ins
Three Strategies • Test Driven Development • Defect Driven Testing • Blitzkrieg
TDD • Write a test that fails • Write just enough code • Repeat
TDD • Drives design • Creates a solid product • Requires enlightenment
• Find a bug • Add a test • Jazz it up DDT
DDT • Inoculates your code • Incrementally builds suite • Retrofit
BK • March across the product • Breadth, not depth • Create templates
BK • Jump start the effort • Same page • Requires enlightenment
Scenario One • New project • Enlightenment TDD + BK + DDT
DDT • No enlightenment Scenario Two • New project
Scenario Three • Existing project • Enlightenment BK + DDT
Scenario Four • Existing project • No enlightenment DDT
Scenario Five • Existing product • Some enlightened developers DDT
Summary • Test categories: Focused & Broad • Test types: Unit & Mock Client • Strategies: TDD, DDT, BK
Your Goal • Pick a strategy • Start within two days • Use it one month • Re-evaluate
Be the change you want to see in the world. -Gandhi
Be the change you want to see in your shop. -Jared
Recommend
More recommend