Test-Driven Development in Microsoft .NET (Microsoft Professional)
|
1 2
| 1. Table of Contents |
| 2. BackCover |
| 3. Test-Driven Development in Microsoft .NET |
| 4. Foreword |
| 5. Introduction | What Are the Benefits of Using Tests? An Example Organization |
| 6. How to Use This Book | How to Use This Book If You Have Never Used NUnit Before If You Are a Manager or Business Analyst |
| 7. Small Steps - A Personal Story | Small StepsA Personal Story |
| 8. Companion Web Site | Companion Web Site |
| 9. Part I: Test-Driven Development Primer | Chapter List |
| 10. Chapter 1: Test-Driven Development Practices | What Is Test-Driven Development? Test Types Simple Design Refactoring |
| 11. Process | Process Test List RedGreenRefactor |
| 12. Summary | Summary |
| 13. Chapter 2: Test-Driven Development in .NET - By Example | The Task |
| 14. Test List | Test List1 Choosing the First Test |
| 15. RedGreenRefactor | RedGreenRefactor Test 1: Create a Stack and verify that IsEmpty is true. Test 2: Push a single object on the Stack and verify that IsEmpty is false. Test 3: Push a single object Pop the object and verify that IsEmpty is true. Test 4: Push a single object remembering what it is; Pop the object and verify that the two objects are equal. Test 5: Push three objects remembering what they are; Pop each one and verify that they are correct. Test 6: Pop a Stack that has no elements. Test 7: Push a single object and then call Top. Verify that IsEmpty returns false. Test 8: Push a single object remembering what it is; and then call Top. Verify that the object that is returned is equal to the one that was pushed. Test 9: Push multiple objects remembering what they are; call Top and verify that the last item pushed is equal to the one returned by Top. Test 10: Push one object and call Top repeatedly comparing what is returned to what was pushed. Test 11: Call Top on a Stack that has no elements. Test 12: Push null onto the Stack and verify that IsEmpty is false. Test 13: Push null onto the Stack Pop the Stack and verify that the value returned is null. Test 14: Push null onto the Stack call Top and verify that the value returned is null. |
| 16. Summary | Summary |
| 17. Chapter 3: Refactoring - By Example | Overview |
| 18. The Sieve | The Sieve Before Refactoring the Code: Make Sure It All Works Refactoring 0: Remove Unneeded Code Refactoring 1: Rename Method Refactoring 2: Add a Test Refactoring 3: Hide Method Refactoring 4: Replace Nested Conditional with Guard Clauses Refactoring 5: Inline Method Refactoring 6: Rename Variable Refactoring 7: Collapse Loops Refactoring 8: Remove Dead Code Refactoring 9: Collapse Loops (Again) Refactoring 10: Reduce Local Variable Scope Refactoring 11: Replace Temp with Query Refactoring 12: Remove Dead Code Refactoring 13: Extract Method Refactoring 14: Extract Method (Again) Refactoring 15: Reduce Local Variable Scope Refactoring 16: Convert Procedural Design to Objects Refactoring 17: Keep the Data Close to Where It Is Used |
| 19. Summary | Summary |
| 20. Part II: Test-Driven Development Example | Chapter List |
| 21. Chapter 4: The Media Library Example | The Skinny Existing Database |
| 22. The First Feature | The First Feature |
| 23. Additional Features | Additional Features |
| 24. Chapter 5: Programmer Tests: Using TDD with ADO.NET | Testing the Database Access Layer |
| 25. The Task | The Task Connecting to the Database Individual Entities in Isolation |
| 26. Testing Relationships Between Entities | Testing Relationships Between Entities Track-Recording Relationship |
| 27. Retrieve a Recording | Retrieve a Recording |
| 28. Test Organization | Test Organization |
| 29. Summary | Summary |
| 30. Chapter 6: Programmer Tests: Using TDD with ASP.NET Web Services | The Task Test List |
| 31. Data Transformation | Data Transformation Data Transfer Object |
| 32. Database Catalog Service | Database Catalog Service |
| 33. Web Service Tests | Web Service Tests Web Service Producer and Consumer Infrastructure |
| 34. Almost Done | Almost Done The Bad News |
| 35. Summary | Summary Emerging Architecture |
| 36. Chapter 7: Customer Tests: Completing the First Feature | Are We Done? Customer Tests |
| 37. Customer Tests for Recording Retrieval | Customer Tests for Recording Retrieval Script 1. Retrieve an existing recording and verify its content Script 2. Retrieve a nonexistent recording |
| 38. Automating Customer Tests | Automating Customer Tests FIT Overview Connecting FIT to the Implementation Automation with FIT |
| 39. Reconciling Viewpoints | Reconciling Viewpoints Track Duration Recording Duration |
| 40. Summary | Summary |
| 41. Chapter 8: Driving Development with Customer Tests | The FIT Script Add a review to an existing recording Implementing AddDelete Review |
| 42. Summary | Summary |
| 43. Chapter 9: Driving Development with Customer Tests: Exposing a Failure Condition | Overview |
| 44. Programmer Tests | Programmer Tests Propagating the Exception Implementing a SOAP Fault |
| 45. Summary | Summary |
| 46. Chapter 10: Programmer Tests: Using Transactions | Overview |
| 47. Programmer Tests | Programmer Tests Transaction Manager |
| 48. Programmer Tests: Catalog Class | Programmer Tests: Catalog Class Refactoring the Catalog class |
| 49. Summary | Summary |
| 50. Chapter 11: Service Layer Refactoring | The Problem Whats Wrong? The Solution |
1 2
|
|
Authors: Newkirk J.W. Vorontsov A. ISBN: 0735619484 Current page: 1 from 85 This Guide are presented on flylib.comOur library present to you materials from book Test-Driven Development in Microsoft .NET. Warning! The page Table of content from this book is informational only! Do not print out this page! Do NOT SUBMIT this page as part of your website or work without confirmation from the authors. You can read the contents of the book, but we strongly recommend that you purchase. or example, you can Buy this book on Amazon.com |
| Buy on Amazon | ||||
Test-Driven Development in Microsoft .NET (Microsoft Professional)
|
||||