Unit Testing: Existing Code

This is the fourth of a four part series where Robert is joined by Phil Japikse to discuss unit testing. This series expands on the 2017 Unit Testing episode. In this final episode, Robert and Phil tie it all together. How do you add Unit Testing into existing code? When should you, as well as when should you not?
Links:
www.skimedic.co...
github.com/ski...
xunit.github.io/
github.com/moq...
Episodes in this series:
Test Driven and Scenario Based Testing
xUnit
Moq Framework
Existing Code (this episode)

[@thatnod]

Wow, you guys look so... Damn. Tired.
Excellent content, so mission accomplished!
Take a break!

[@gedmoretta6825]

Ashley J. Lawson Tired? I think you mean drunk. I’m surprised the Channel 9 editors allowed this to be published. This is probably the worst Toolbox video I’ve watched.

[@asifsarwer-1]

Best series on Testing

[@GaryJohnWalker1]

Liked the moq episode - moq's not as fearsome as it can seem at first. And why xunit should really replace WHAT'S CURRENTLY the "automatic" choice of nunit. But this was the most useful ep. Don't try and pay off all the technical debt right now. Concentrate on the one bit you are changing.

[@bbry323]

I really enjoyed the 'multi-line comment' short segment 😇 @~830mins

[@technothirsty8105]

Is it possible to do unit testing of my asp.net project??

[@JohnLudlow]

Yes, since your project emits a .dll assembly. Though your life will be simpler if you move most of your non-web code to class libraries, leaving only a thin shell in your actual asp.net project (what I call the application layer).

[@akostipecukazuje4862]

similar as any C# code...

[@user-yr1uq1qe6y]

/* before .net even */

[@kurkuries]

I think I'm the first viewer...😃