A newbie on another mailing list (Ron Jeffries) asked a question recently. It inspired the first new paragraph in the following diatribe in a while. Test...
... It's a nice writeup. Rather too limiting, but perhaps a good starting place for some. I'm really not quite that much in favor of forgetting everything one...
... Uh, yeah, it's kind of in a starting-place position. ... Exqueeze me? What line item advocated forgetting everything you know? The point, again: The time...
... I'm all for simplicity. But I think the time for everything you know is always. So while it might be a really good beginner's mind thing to do the minimal...
Why do I care if my test failed for the "right reason"? Shouldn't I just care about red bar/green bar? Since we're not terribly particular about whether they...
... I hadn't noticed the irony. Getting the test to fail for the correct reason is indeed more important than passing for the correct reason! At red bar time: ...
... The test might fail because it is wrong. This introduces a specification defect that your production code may then specify. Now you have a production...
But the arguments you make also hold for a test which passes unexpectedly, that is, the test may be wrong or one's mental model of the local design is wrong. ...
I'm probably splitting hairs, but I'm still not sure I agree. Let's say I'm progressing nicely: 1. Write test for a small bit of functionality 2. Stub out (if...
... Absolutely. -- Edmund Schweppe -- schweppe@... -- http://schweppe.home.tiac.net The opinions expressed herein are at best coincidentally related to ...
Edmund Schweppe
schweppe@...
Feb 10, 2004 11:04 pm
413
... 1.5 compile, and see if there was stuff to stub out. If you think you know the target objects, expect a syntax error for any assumption of facts not in ...
... If the test fails for the right reason, then it will pass for the right reason. If the test fails for the wrong reason, we may end up writing code that...
... But the arguments you make also hold for a test which passes unexpectedly, that is, the test may be wrong or one's mental model of the local design is...
eXtremos: Someone elsewhere on the 'net read /TDD/, and asked how to design and code user interfaces. I replied: The purpose of Programmer Tests is to make...
I'm replying here, only because I didn't like the outgoing e-mail address Yahoo! chose when I tried to reply to the SV group. ... Any time you fake/stub a...
... How often do we replace GUI controls with Mocks? ===== Phlip http://www.xpsd.org/cgi-bin/wiki?TestFirstUserInterfaces __________________________________ Do...
quite often in the .Net world to test the code-behind. Although I usually wrap them in an interface so I don't have to carry /all/ the GUI baggage around with...
Hello to everybody. I am learning TDD right now, with David Astels's book, but using C# for development. I have some problems trying the samples for developing...
I have some problems using EasyMockNET with C#, trying the samples from Astel's book. When I try to link the view and the controller in GUI using a call to a...
I also have problems in using EasyMockNET when I uses ArrayList as parameters of the methods. If anybody wants, I can send him a demo project to see the...
... I have bootstrapped the TFUI Principles for an Exalted Dialog Box in C#. To use this, start a Windows app, paint a single dialog called Form1, and paint on...
... Let's go at this from first principles: - Inspecting a window, instead of writing a test, sucks. - mocking a window won't test. The mock will tell you what...
I am having problems, doing TDD with C#, when using mocks. I have try with EasyMockNET and with NMock, and I have similar problems with methods with ArrayList...
Hi Juan, let me jump in here and send me your zip file via private mail. Please describe exactly what you expect your code to do and what it doesn't do. Maybe...
... Please send it to me, then start a new project using this technique: http://groups.yahoo.com/group/TestFirstUserInterfaces/message/426 Don't throw your...