I think this is in keeping with real unit tests which should have as few dependencies as possible. I know when I figured out methods to mock or stub out dependencies on databases especially my unit testing running time went down by a factor of 10 or 100. And because I could close the feedback loop more quickly I wrote more tests and ended up with a lot less sneaky defects. Now if I see some dependency on the filesystem or some other object I'll try to find the fastest way to remove it so I can right true unit tests instead of less useful integration tests. Understanding and writing true unit tests has really moved my skills as a developer along. Now I just need to impart that experience to many of my direct reports. And I still write some integration, functional, or end to end GUI tests, I just let Cruisecontrol run them for me.
Flat View: This topic has 50 replies
on 51 pages
[
«
|
456789101112
|
»
]
Previous Topic
