Hehehhe.... I'll see how the article goes first. ;)
Thanks,
James
On 11/9/06, Anderson, Kelly <kanderson@...> wrote:
>
> Whoever writes the book/article gets to pick the names in the end... :-)
>
>
> So, who will write the book first, John or James? I know it won't be
> me... :-)
>
> -Kelly
>
>
>
>
>
>
> E-Mail messages may contain viruses, worms, or other malicious code. By
> reading the message and opening any attachments, the recipient accepts full
> responsibility for taking protective action against such code. Sender is not
> liable for any loss or damage arising from this message.
>
> The information in this e-mail is confidential and may be legally
> privileged. It is intended solely for the addressee(s). Access to this
> e-mail by anyone else is unauthorized.
>
>
>
[Non-text portions of this message have been removed]
Whoever writes the book/article gets to pick the names in the end... :-) So, who will write the book first, John or James? I know it won't be me... :-) -Kelly ...
Hi, ... I'll be including several examples in the paper. An example of "over mocked" is one of those tests where so much is mocked or stubbed out, that no real...
I think I understand what you mean by over-mocking, but I don't think you could over-mock to the point where you're testing nothing. I think a different way...
Well said Dylan. I would add that over mocking might be a perception that to test such a small subject it requires too much mocking. That is to say that the...
... That would be a really bad smell, but then mocking within the class you're testing is already bad. One case you might also want to add is unit-testing the...
Oh, my goodness, I've seen them. Mocking a factory that mocked several calls to each of several factory methods, which return several mocks, each with several...
Tim Ottinger
tottinge@...
Nov 3, 2006 2:53 am
Wouldn't that be better called The Glutton, a test that takes too large a bite at a time? S. ... Steve Freeman M3P Limited. http://www.m3p.co.uk Winner of the...
... OK, here's a few, following your style. I have encountered all of these "in the wild". * The Nitpicker - A unit test which compares a complete output when ...
Hi, Frank, ... It strikes me as a great list (and I'm ashamed of how many of them I've written!) Particularly if James incorporates your list, I'm very eager...
Hahaha... That's a great list Frank... I already identified a few under different names, but I like yours better. ;) The Loudmouth is one I have seen quite a...
Excellent list! ... Couldn't agree more ... This one does not seem as obvious as the rest but it really doesn't seem like a good thing to do so I guess you're...
I got so inspired that I wanted to fill in one more. I realized all this cheering and agreeing doesn't really contribute much :) I'm not as good as inventing...
Three more that I just thought of: The bounty hunter: Making sure to exercise all code in order to reach the required level of X% testcoverage. But not really...
... I dug up an example of this from my own current project: private DOMOutputter dom = new DOMOutputter(); public void testConversion() throws Exception { ...
... This one can be really insidious on Windows... retrieving lists of files from NTFS always come back in alphabetical order, but from FAT32 they come back in...
Hello Frank, Thanks, yes I found them useful (if nothing else, very entertaining.) ... guess this means I'll need to go do some refactoring on my test code... ...
Hi All, I've begun writing the paper, but I have a small problem with one of the patterns, The Liar. I have seen it before, but I'm not sure about the ...
... It seems to me there are a huge number of anti-pattern candidates listed here. I think once you've got them all green you should refactor your patterns,...
... Actually you will find this pattern in quite a lot of my code as I know the Ruby test/unit framework will do The Right Thing if an exception of any sort...
John, I've seen this in my own code sometimes as well, but I don't really like it. It's mostly in places where I can't figure out really what I want to test,...
Hmm, I have been doing TDD before there was a name for it. When TDD came along I said, Ah, so that is what I have been doing. But I have always had small...
... Well, that is why I don't like to be testing my code like that. I guess, if you name it well, it may not be as great a problem as if you don't, but in...
Well, I wasn't cool before cool was cool, but the thing that bothers me is twofold: 1) Insufficient specificity - You should look for some specific failure or...
Tim Ottinger
tottinge@...
Nov 9, 2006 4:31 pm
... This example and the ruby one, I'd probably still put the assertNotNull in, because someone coming after is going to look at it and wonder where the...
Hi John, ... I think most frameworks handle this quite well, failing the test and displaying a message and stack trace. ... I don't believe this was a question...
Offline 
Send Email
