Introduction toUnit TestingGil Zilberfeld, Product Manager7-Dec-2011
Bugs   The curse of developers  How do we deal with them?
Types of Testing• QA  • Manual tests  • Acceptance tests• Developer  • Integration tests  • Unit tests
Manual Tests•   Slow•   Do not scale•   Encourage forgetfulness•   Immoral
Automated Tests• Run all the time• Don’t complain• Don’t forget
Why Unit Test?• Quick feedback     • Low TCO• Confidence to      • Small setup  change your code     overhead• Quicker tha...
xUnit Frameworks• Test Identification• Test Runner• Asserts
.NET xUnit Frameworks•   NUnit•   MSTest•   xUnit•   MbUnit
Demo
Test Driven Development
Test Driven Development•   Same tools•   Think before you act•   Great coverage•   Improved design•   Give it a try
Questions?www.typemock.com    www.gilzilberfeld.comtypemock.com/blog     gilz@typemock.com@typemock                  @gil_...
Upcoming SlideShare
Loading in …5
×

Introduction to unit testing

1,220 views
1,145 views

Published on

Published in: Technology, Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,220
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
15
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Introduction to unit testing

  1. 1. Introduction toUnit TestingGil Zilberfeld, Product Manager7-Dec-2011
  2. 2. Bugs The curse of developers How do we deal with them?
  3. 3. Types of Testing• QA • Manual tests • Acceptance tests• Developer • Integration tests • Unit tests
  4. 4. Manual Tests• Slow• Do not scale• Encourage forgetfulness• Immoral
  5. 5. Automated Tests• Run all the time• Don’t complain• Don’t forget
  6. 6. Why Unit Test?• Quick feedback • Low TCO• Confidence to • Small setup change your code overhead• Quicker than • It’s not bugs if debugging it’s caught before• Knowing your QA code works • Go faster
  7. 7. xUnit Frameworks• Test Identification• Test Runner• Asserts
  8. 8. .NET xUnit Frameworks• NUnit• MSTest• xUnit• MbUnit
  9. 9. Demo
  10. 10. Test Driven Development
  11. 11. Test Driven Development• Same tools• Think before you act• Great coverage• Improved design• Give it a try
  12. 12. Questions?www.typemock.com www.gilzilberfeld.comtypemock.com/blog gilz@typemock.com@typemock @gil_zilberfeld

×