Mon premier blog

Growing Object-Oriented Software, Guided by Tests Nat Pryce, Steve Freeman
Publisher: Addison-Wesley Professional

I've been reading Growing Object-Oriented Software Guided by Tests during August. Code passing a good set of tests in a branch can give any coder the confidence that a clean get from source control will result in a successful build of useful software. "Growing Object-Oriented Software Guided by Tests" by Steve Freeman and Nat Pryce is the most useful, serious and well-written book I've read in last couple of years. Sustainable Test-Driven Development - Part 1 - Listening to the tests. Please find the notes gathered by reading the book "Growing Object-Oriented Software, Guided by Tests". Tests should be: · Expressive. UncleBob's Ruby Midwest keynote “Architecture – The Lost Years” attributes one source of this idea to Ivar Jacobsen's 1994 book Object Oriented Software Engineering : A Use Case Driven Approach (2nd-hand hardbacks cheap I first came across this technique in “Growing Object-Oriented Software, Guided By Tests” (http://www.amazon.co.uk/Growing-Object-Oriented-Software-Guided-Signature/dp/0321503627/ref=sr_1_1?ie=UTF8&qid=1354692166&sr=8-1). In 2010 I read 37 books of all different flavours but my favorite software book of the year was definitely Growing Object-Oriented Software, Guided by Tests by Steve Freeman and Nat Pryce. Growing Object-Oriented Software, Guided by Tests. In the middle of your post I was thinking the point of missing tests, maybe because of I'm currently reading Growing Object Oriented Software, Guided by Tests. Growing Object-Oriented Software, Guided by Tests Addison-Wesley Professional | ISBN: 0321503627 | PDF | 384 pages | 4.1 MB Book Description Test-Driven Development (TDD) is now an establis. It is with some surprise, then, that I catch myself re-reading a technical book: Nat Pryce and Steve Freeman's Growing Object Oriented Software Guided By Tests. Here's the short version: If you write code then go get this book and spend some time absorbing the ideas in it. It's all about TDD (test-driven development) and OOD. It's well written and easy to read, but grokking it all will take time and practice.