Erick,
I generally don't test the framework itself. If it changes, as F# has a lot in the past year, I generally copy the assembly locally, somewhat like freezing Ruby Gems. If the framework changes on you, that's somewhat outside the scope of my unit tests, imho. Ryan From: [email protected] [mailto:[email protected]] On Behalf Of Erick Thompson Sent: Saturday, March 20, 2010 9:07 AM To: [email protected] Subject: Re: Good Code Requires Few Unit Tests Ryan, What about potential updates to the .NET framework? While it doesn't happen often, there are times when functionality is changed due to security issues. Erick On Fri, Mar 19, 2010 at 8:06 PM, Ryan Riley <[email protected]> wrote: Sorry, bad use of the term. I meant unit tests you would actually keep around. When working with F#, I often just run some tests or FsCheck in FSI and don't actually write tests I'm going to keep. That's not always true, but for pure functions, once I know they work, I don't have to worry about something else affecting them. From: [email protected] [mailto:[email protected]] On Behalf Of Justin Bozonier Sent: Friday, March 19, 2010 3:32 PM To: [email protected] Subject: Re: Good Code Requires Few Unit Tests Roy, are you saying interfaces should provide lots of functionality? Ryan, what do you mean by "persistent unit tests"? Also a point that Robert Ream and Kelly Leahy made me realize is, Does the author mean *FEW* unit tests or *FEWER*? It's an important distinction and I'm honestly not very sure which he meant. On Fri, Mar 19, 2010 at 2:53 PM, Roy Osherove <[email protected]> wrote: not totally wrong, but hardly right.. yes, your should have fewer interfaces that should have tests against them, but, you could have many many tests against those interfaces if they provide lots of functionality.. I agree that one could write many BAD tests for a very fractured system, but, tests can be abused even against a well designed system - that is - when you're trying to test things at the wrong level (to low level) you will always end up with more tests that cover less ground, and might overall not really check full unit-of-work, but only units. On Fri, Mar 19, 2010 at 11:47 PM, Justin Bozonier <[email protected]> wrote: What do you guys think about this? http://andreyf.tumblr.com/post/459323557/good-code-needs-few-unit-tests -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:altnetseattle%[email protected]> . For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en. -- Thanks, Roy Osherove www.TypeMock.com <http://www.typemock.com/> - Unit Testing, Plain Smart Author of "The Art Of Unit Testing" (http://ArtOfUnitTesting.com <http://artofunittesting.com/> ) A blog for team leaders: http://5Whys.com <http://5whys.com/> my .NET blog: http://www.ISerializable.com <http://www.iserializable.com/> Twitter: http://twitter.com/RoyOsherove +972-524-655388 (GMT+2) -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:altnetseattle%[email protected]> . For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en. -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:altnetseattle%[email protected]> . For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en. -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:altnetseattle%[email protected]> . For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en. -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en. -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
