be a legacy code unit test ninja with typemock isolator
DESCRIPTION
Roy Osherove teaches how to use Typemock Isolator to write unit tests for legacy code that cannot be changed.23-11-2010TRANSCRIPT
1
Roy Osherove CTO, Typemock
Unit Testing Legacy CodeWith Isolator
@RoyOsherove
2
Twitter : Ask @Typemock under #Legacy
Asking Questions
3
Answer Survey
Giveaways:2 Isolator Licenses
Our ApplicationBlogEngine.NET
Download the code Follow Along
http://blogengine.codeplex.com/
What shall we test?
Blog Post Manager Ping\Trackback.Send(..)Ping\Trackback
Servers
Legacy Code Ahead Lots of Dependencies Unknown Beforehand Many Rules Don’t Apply Tests are longer, and
harder to read Better to start with
integration tests
7
Demo Excavating Code with Isolator
Wishful Invocation Get dependency
exception Choose Dependency from stack
FAKE dependency
Summary
Approach Legacy With Caution Choose the right level of isolation Use Broad Strokes when Faking Legacy
MaintainabilityReadability
See tests fail and passtrust
9
More Advice
Typemock Forumshttp://forums.typemock.com/
Support staff Blog.typemock.com
10
Vs. Competitors
VS Versions• Supports vs
2005-2010• Supports .NET
2.0 – 4.0
Fakes• Any Legacy
Code• IntelliTest
Suggestions
3rd party• Works with
other profilers• Extensible
IntelliTest• Extensible
CThru
12
Easy, Correct & Effective Unit Testing
“Typemock - My testing tool of choice. Each time I use it, I rediscover its power, and I'm amazed.
Great tool!”Jason C Divis, @CodingOfficer
13
Twitter : Ask @Typemock
Asking Questions
14
Answer All Survey Questionsafter this webinar finished
Giveaways:2 Isolator Licenses
