I've taken several stabs at testing GUIs, and still do a certain amount of it, but am becoming skeptical of the endeavor. This isn't because of technical...
... Not in card shuffling. Anyway, drip under pressure and all that ... I'm just some guy talking about what I'd do. ... I'm not sure what you're envisioning...
... Lucky for me I am at home reading this and have access to my books. I am familiar with static code analizers but I am not sure what is meant by "model...
I agree completely, and that's why I think I like the Humble Dialog approach. That approach practically forces you to keep business logic out of the GUI,...
... That's the thing: When mundane controls provide an "ownerdraw" system, they provide back-doors to override part of their paint events. (That's how your...
I've been developing a web app in ASP.NET using TDD. For myself, I've come to realize that you get the best benefits of TDD if you push as much business logic...
... Okay, you're the expert on TDD :-). Definitely more so than I. ... Sounds like you've already picked out an algorithm (that's not a problem description,...
... As a rule, I'd ignore the randomness issue, trusting that I have or can get a random number generator that will be random. I would instead test sequence of...
I am sure that I will have questions. Would you prefer that I ask them to you in this group or should I email them to you directly? If email, let me know what...
Hi, I've been playing again with "zero button testing" - correctness coloring as you type, much like David Saff's Automated Continuous Testing. The latest...
When do you change your unit tests after refactoring? For example, I run my tests; get a green bar. Then I refactor by moving a method from one object to...
TDDers: Try this: Install Visual Studio 7, and install NUnit 2.2 Double click on: C:/Program Files/NUnit 2.2/src/samples/csharp/csharp-sample.csproj Hit <F10>....
Should you not amend the Unit tests to reflect the desired result of the refactoring prior to actually implementing the refactoring (if appropriate)? If it is...
According to what I've been reading about refactoring, the idea is to produce "better code" that works the same. So the cycle is "green bar; refactor; green...
Not if it's going to give you a red bar before you make the change. Fowler's book explains this in some detail, but let's take the example of moving a method...
... Actually, that should be: File webXml = new File("/home/george/workspace/MyProj/WebRoot/WEB-INF/web.xml"); assertTrue(webXml.canRead()); ServletRunner sr =...
... I fixed it using Project -> Add Reference. Now I wonder why I can't just execute the test cases - why are they a DLL, and am I expected to I will fix this...
... I'm glad you got to the next step. Enjoy. ... Of course! If you're in Toronto, Ottawa or Vancouver any time soon, you can even buy a signed copy, if you...
... Yay! We got a green bar. It turns out we don't need to register the JspServlet, but we *do* need to include the commons-el.jar on the classpath. <sigh> ...
... When the merged or derived thing grows important enough to document its interface. If it ain't important, then it's just an encapsulated detail of the ...
John Roth wrote:- ... Whilst agreeing with the sentiment here, I don't see that an Extract Method refactoring should produce a public method, IME it always...
... Robert, I have found (through both advice and experience) that cruft builds up in the unit tests the same way it does in production code. Therefore unit...
All, [[This is the first announcement of this project on this list. If you're interested, please visit http://pag.csail.mit.edu/continuoustesting and...
... change. David, I'm still new at this, working solo and only 16 months, but... Why couldn't you: 1) start from green bar 2) move the unit test, 3) get a red...
As long as we are refactoring, we are not changing behaviour, and we should not need to add new tests. I see why you want to add the new tests, but aren't they...
