开云体育

Maybe I'm just dense, but: what is it about this that is particular to TDD? Seems to me that monkey patching without tests is *fuck all* more dangerous than writing a test, making it pass in the

Snort. This is a continuing issue for the Python developers as well. John Roth

Dennis, You should pair that with The Mikado Method (mikadomethod.org) - George -- ---------------------------------------------------------------------- * George Dinwiddie *

One of the "Aha!" Epiphanies of a programmer I was working with, was the realization that a unit test only needs to test a "unit". He had been setting up real-life data, when a little "fake" data

I believe that this is one of the most essential books, no matter if you have to deal with legacy code (everyone has eventually, anyway).

The following are some books I recommend to developers new to Agile software development. This book is new, pretty complete, and easy-to-read about adopting agile software development: The Agile

Pretty easy to find out. Valgrind gives us the call-stack of the allocation that leaked, and most code is only executed by a few tests. (Google "microtest" to see why (and "Mike Wrote Tests").) Some

I guess this could a "per language" thing... In perl, unless you run with -w (which you should), you never even get told about using uninitialized variables, and _every_ variable is initialized

Actually... it happened on every one. As soon as you touch the heap, you have changed the system state. If it's a GC'd language this isn't quite so problematic, but you still get other resource

I've seen more of the opposite problem. When previously isolated tests show up a bug when run together - because there was some state that should have been reset that wasn't. A few years back I spent

I think it's called "monkey patch" for a reason ... Ron Jeffries www.XProgramming.com There's no word for accountability in Finnish. Accountability is something that is left when responsibility has

I've seen this in Python tests where developers monkey-patch things and forget to set them back or otherwise muck with global state. This has been the result of design issues. -- David blog:

Hi everyone! John, usually I don't find the case "this test corrupts that test", and I wrote thousands of tests. Any example/case? Angel "Java" Lopez @ajlopez gh:ajlopez

John C, While I agree with you, I don't see the point of your post. You can produce elegant code on Windows or on Unix. You work with what you've got is all. John D.

I found goos to be not so much a "how to write tests" book, but more of an illustration of how code can evolve when using TDD. 聽My main criticism聽with the book is that it is easy to lose the big

Google's test framework for C++ allows for "death tests" where a separate process is spun up, executed to run a test, and stderr (I think) + result code examined. if the test doesn't cause that

Most of them invest way too much effort to make up for the deficiencies of the Windows Operating system. The Component in a Computer tasked with managing concurrency, task separation, and ensuring

Two books that I can recommend: Osherov, The Art of Unit testing jbrains, Responsible Design for Android - on going work, somewhat builds on GOOS

Hmmm... I know a number of good books on TDD. I've not read any of them all the way through. I think reading these books and mastering TDD are orthogonal. Mastering requires practicing, not reading.

TDD By Example +1, Refactoring +1 GOOS +2 Clean Code +1 Agile Software Development, Principles, Patterns, and Practices -- Abra鏾s, Josu� http://twitter.com/josuesantos