Downloaded 12 times
Uploaded byMiguel Alho
Tdd01 a simple intro to tdd
This document provides an overview of agile testing and different types of tests used in agile development. It discusses testing in an agile context to respond to change through continuous testing with fast feedback. Various types of tests are described, including functional, unit, integration, and usability tests. Unit testing is explored in more detail, covering concepts like test structure, isolation, and characteristics of good unit tests. The document also distinguishes between unit testing and test-driven development (TDD), showing TDD follows unit testing in a particular order.
Tdd01 a simple intro to tdd
- 1.
- 2.
- 3. had a clientwho knew what he needed? question 1
- 4. been in aproject with no change in requirements? question 2
- 5. predicted every problem 3months in advance? question 3
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13. reduce the risk! usethe agile iterative cycle
- 14.
- 16. know what worksat any given moment
- 19.
- 20. Functional Tests Examples Story Tests Prototypes Simulations UnitTests Component Tests Exploratoy Testing Scenarios Usability Testing UAT A/B Performance & Load Testing Security Testing “ility Testing” Automated & Manual Automated Manual Tools Q2 Q3 Q1 Q4 Business Facing Technology Facing SupportingtheTeam CritiqueProduct
- 21. Functional Tests Examples Story Tests Prototypes Simulations UnitTests Component Tests Exploratoy Testing Scenarios Usability Testing UAT A/B Performance & Load Testing Security Testing “ility Testing” Automated & Manual Automated Manual Tools Q2 Q3 Q1 Q4 Business Facing Technology Facing SupportingtheTeam CritiqueProduct
- 22. Coding Unit Testing Program Unit Design PhysicalDesign Logical Design User Requirements Integration Testing System Testing Acceptance Testing Verifies Verifies Verifies Verifies
- 23.
- 24. What Is A UnitTest?
- 25. Unit Tests • Testsa single unit of code (typically a method) • Tests the unit of code in ISOLATION • Tests that the code behaves as expected
- 26. Unit Tests • It’sstill code • Code that tests code • Exercise SUT, check behaviour • Concepts: Test Class, Test Method
- 27.
- 28.
- 29.
- 30. Unit Tests • Shouldbe fast (< 10 ms) • Should be consistent (same result always) • Should run in memory (no db, file access) • Should run in any order (no dependencies on other tests)
- 31. Impacts • Fast Feedback •Cleaner design • Code and componente decoupling • Confidence • Executable documentation, with usage samples • Reduce regression
- 33.
- 34.
- 35. TDD is unit testing (in aparticular order)
- 37.
- 38.
- 39.
- 40.
- 41.
- 42. Books • Pragmatic UnitTesting In C# with Nunit • Growing software guided by tests • The art of unit Testing • Testable Javascript • Quality Code • Xunit Patterns