• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
TDD 0 to 60 - An Introduction to Test-Driven Development in .NET
 

TDD 0 to 60 - An Introduction to Test-Driven Development in .NET

on

  • 2,245 views

If you've heard of Test-driven Development, and you're wondering what all the fuss is about, this slidedeck will provide a code-centric introduction to the concepts, tools, and practices of TDD in the ...

If you've heard of Test-driven Development, and you're wondering what all the fuss is about, this slidedeck will provide a code-centric introduction to the concepts, tools, and practices of TDD in the .NET framework.

We'll start with the basics of setting up a unit testing framework and writing the first test, then we'll move on to techniques for mocking dependencies and demonstrate patterns like Dependency Injection that will help you move past testing just the basics.

We invite you to download the full webinar replay at http://pillartechnology.com/content/webinardetail/id/15 which includes live demonstrations. After viewing the webinar replay, you should be able to sit down and start writing tests that will drive the design of your application, creating loosely-coupled and testable code.

Statistics

Views

Total Views
2,245
Views on SlideShare
2,180
Embed Views
65

Actions

Likes
1
Downloads
36
Comments
0

2 Embeds 65

http://www.slideshare.net 64
http://www.slashdocs.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    TDD 0 to 60 - An Introduction to Test-Driven Development in .NET TDD 0 to 60 - An Introduction to Test-Driven Development in .NET Presentation Transcript

    • http://www.flickr.com/photos/purplepick/2554134479/ TDD 0 to 60 An Introduction in Test-Driven Development Michael Joseph Kramer Pillar Technology in .NET
    • What do you mean by “unit test”? • code tests code • small • fast • independent http://www.flickr.com/photos/ugocei/6420197/
    • the whole truthiness • Anything I can do with a unit test, I can do with a debugger. • It’s an ivory tower activity, not something real businesses do. • Unit testing isn’t for small businesses. • Unit testing isn’t for the enterprise. • We don’t need no stinkin’ unit tests. We have a QA team! • We don’t need no stinkin’ QA team. We have unit tests! • Writing tests will take me longer, which makes it cost more. • Most of the stuff I write isn’t interesting enough for a unit tests. It’s only for complicated stuff. • Unit testing prevents you from writing crappy software. • Everything I have ever learned about software development is wrong. http://www.flickr.com/photos/thelastminute/142252337/
    • What do I need? • NUnit • MbUnit • MsTest • xUnit.net http://www.flickr.com/photos/17258892@N05/2588347668/
    • http://www.flickr.com/photos/lynac/321100379/
    • AAA ain’t just the auto club Arrange – Set it up! Act – Call It! Assert – Verify it worked!
    • http://www.flickr.com/photos/ethomsen/2815081394/
    • Is this TDD???
    • http://www.flickr.com/photos/37612915@N00/350716275/
    • only refactor green tests! http://www.flickr.com/photos/jshultz/118841012/
    • http://http://www.flickr.com/photos/roadsidepictures/469271408//
    • Weak. My code uses a database... http://www.flickr.com/photos/helios89/1373343153
    • Dependencies • inject the dependency • replace with a stub http://www.flickr.com/photos/leecullivan/141114012/
    • http://www.flickr.com/photos/victius/4064996780/
    • Why can’t I just go to the database? http://www.flickr.com/photos/richpix/1386265680/
    • Mocking: not just for when your manager out of the room • a mock knows if your test passed • behavior, not state • void methods • brittle http://www.flickr.com/photos/mariaclarah/927759528/
    • http://www.flickr.com/photos/8829172@N02/4010684609/
    • Mocks aren’t Stubs, abridged • Stubs vs. Mocks, in a nutshell: – Stubs: return dummy data – Mocks: Test passes or fails based on what the method does, not what it returns – Test Double or Fake: Generic terms for either a mock or stub I.E., a mock can make a test fail, a stub can’t. Full Version: http://martinfowler.com/articles/mocksArentStubs.html
    • http://www.flickr.com/photos/marcobellucci/3534516458/
    • Our Next Steps • Upcoming Webinars: Please visit pillartechnology.com/events • All of the webinar content is available to your business in a 1-2 day on-site workshop or as a “lunch and learn” format. Please contact us for details. • Visit www.pillartechnology.com/events to access presentation slides and full archived broadcasts of past webinars. • Twitter.com/agilesoftware • Blog: www.pillartechnology.com/blog • LinkedIn: Join the Agile Enthusiast Group on LinkedIn: http://bit.ly/agilegroup • YouTube: http://www.youtube.com/user/PillarTechnology • Phone: (888) 3-pillar • Web: pillartechnology.com • Email: info@pillartechnology.com