Test-driven Development Practices in White Box Test Automation


Published on

Test-driven development is a software development process that relies on the repetition of a very short development cycle. This process is heavily emphasized by those using Agile development methodologies. White-box testing (also known as clear box testing, glass box testing, transparent box testing, and structural testing) is a method of software testing that tests internal structures of an application, as opposed to its functionality. In this session, we will learn how to use white box test automation in the form of test-driven development at the unit, integration and system levels of the software testing process.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Test-driven Development Practices in White Box Test Automation

  1. 1. Test-driven DevelopmentPractices in White Box TestAutomationErvin LohALM Program ManagerK365Labs Sdn Bhd
  2. 2. Typical result?
  3. 3. What is Test-driven Development?“Test-Driven Development seeks specification, not validation, letting you think through your design before you write your functional code” - Scott Ambler“Test-Driven Development is a powerful way to produce well designed code with fewer defects” - Martin Fowler
  4. 4. Test-driven Development Stages In Extreme Programming Explored (The Green Book), Bill Wake describes the test / code cycle: Write a single test Compile it. It shouldn’t compile because you’ve not written the implementation code Implement just enough code to get the test to compile Run the test and see it fail Implement just enough code to get the test to pass Run the test and see it pass Refactor for clarity and “once and only once” Repeat
  5. 5. Test Driven DevelopmentThe motto "Red, Green, Refactor."
  6. 6. Get Agile – Test DrivenDevelopment PracticesTools For Agility, Kent Beck Tools
  7. 7. The Demo Scenario The Configuration An application, Tailspin Toys that builds in Visual Studio 2010 A fully configured Visual Studio 2010 Premium and Team Foundation Server 2010 environment What’s Needed A lot: tests and builds
  8. 8. Step 1: Unit TestA method bywhich individualunits of sourcecode are tested todetermine if theyare fit for use.
  9. 9. Unit Tests with Visual Studio 2010
  10. 10. Step 2: Test Impact AnalysisA method toidentify the teststhat need to berun for the latestcode change.
  11. 11. Integrating Unit Tests andTest Impact Analysis with Visual Studio 2010
  12. 12. Step 3: Code CoverageA method todescribe thedegree to whichthe source codeof a program hasbeen tested.
  13. 13. Integrating Unit Tests andCode Coverage with Visual Studio 2010
  14. 14. Step 4: Build AutomationAn act ofautomating awide variety oftasks such ascompilingcomputer sourcecode into binarycode, packagingbinary code, andrunning tests.
  15. 15. Integrating Build Automation and Unit Tests
  16. 16. Quality Indicators 91 80 76 71 60 51 56 40 32.5 20 19 18 12 9 8 Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5
  17. 17. Starting Test Driven DevelopmentCreating a cultural change is hard… ….. and it can be done
  18. 18. Questions & Answers
  19. 19. ResourcesBrian Marick’s Sitehttp://www.testdriven.comGuidelines for Test-Driven Developmenthttp://msdn.microsoft.com/en-us/library/aa730844(v=vs.80).aspxUsing TDD with ASP.NET MVChttp://msdn.microsoft.com/en-us/library/ff847525.aspxApply Test-Driven Development to your Database Projectshttp://msdn.microsoft.com/en-us/magazine/cc164243.aspxImprove the Design and Flexibility of Your Project with Extreme ProgrammingTechniqueshttp://msdn.microsoft.com/en-us/magazine/cc163982.aspx
  20. 20. Recommended Books test-driven development: A Practical Guide Dave Astels Prentice-Hall/Pearson Education, 2003 ISBN 0-13-101649-0 Review available on my web-site ______________________________________ Test-Driven Development: By Example Kent Beck Addison-Wesley, 2003 ISBN 0-321-14653-0
  21. 21. Recommanded BooksRefactoring: Improving the Design of Existing CodeMartin FowlerAddison-Wesley, 1999ISBN 0-201-48567-2__________________________________Test-Driven Development in Microsoft.NETJames W. Newkirk; Alexei A. VorontsovMicrosoft Press, 2004ISBN 0-7356-1948-4xUnit.net & xUnit Test Pattern
  22. 22. We value your feedback!Please remember to complete theoverall conference evaluation form andreturn it to the Registration Counter.