tag:broadcast.oreilly.com,2008-08-07://53 2010-05-30T04:47:36Z Movable Type Pro 4.21-en tag:broadcast.oreilly.com,2010://53.39978 2010-05-30T04:47:36Z 2010-05-30T04:47:36Z

While Extreme Programming remains a valuable template for project success, the decade of its adoption also saw the rise of many dilutions and derivatives. This post debunks some common myths about TDD.

Phlip Plumlee http://www.oreilly.com/catalog/9780596510657/ While Extreme Programming remains a valuable template for project success, the decade of its adoption also saw the rise of many dilutions and derivatives. This post debunks some common myths about TDD. tag:broadcast.oreilly.com,2010://53.39798 2010-05-04T04:46:00Z 2010-05-04T04:46:00Z

My last post showed how to mock a webservice. When you have more than one webservice, all their common code, tests, and mocks should remain DRY. This post demonstrates a ruthlessly effective test pattern that forces many different interfaces to behave as similarly as possible, using the minimum possible test code.

Phlip Plumlee http://www.oreilly.com/catalog/9780596510657/ My last post showed how to mock a webservice. When you have more than one webservice, all their common code, tests, and mocks should remain DRY. This post demonstrates a ruthlessly effective test pattern that forces many different interfaces to behave as similarly as possible, using the minimum possible test code. tag:broadcast.oreilly.com,2010://53.39797 2010-05-04T03:02:39Z 2010-05-04T03:02:39Z

This post shows how to write a web service using Test-Driven Development. Our source code example is the exemplary active_merchant contribution to Ruby on Rails. It reveals how developer tests can correctly attack remote web services. Programmers writing clients (or servers) for any kind of web service should use these techniques. My next post will extend this one into the Abstract Test Pattern.

Phlip Plumlee http://www.oreilly.com/catalog/9780596510657/ This post shows how to write a web service using Test-Driven Development. Our source code example is the exemplary active_merchant contribution to Ruby on Rails. It reveals how developer tests can correctly attack remote web services. Programmers writing clients (or servers) for any kind of web service should use these techniques. My next post will extend this one into the Abstract Test Pattern. tag:broadcast.oreilly.com,2009://53.35911 2009-04-20T19:31:27Z 2009-04-20T19:31:27Z

Well-factored code often has many small functions. If each adds value, and doesn't just pass the buck, then what do they all do? Typically, they contract their input by making it more specific. Then they delegate these specific data to a delegatee.

Phlip Plumlee http://www.oreilly.com/catalog/9780596510657/ Well-factored code often has many small functions. If each adds value, and doesn't just pass the buck, then what do they all do? Typically, they contract their input by making it more specific. Then they delegate these specific data to a delegatee. tag:broadcast.oreilly.com,2009://53.35728 2009-03-29T02:40:14Z 2009-03-29T02:40:14Z

I have upgraded several Rails 1.2.x programs to 2.x. This can be quite a leap, and some of the steps are counterintuitive, so this post attempts to put everything together, like a recipe. I'd also like to hear more stories about upgrading platforms; such stories may indeed emend my suggested hacks and tweaks. Yet the point of unit tests, and TDD, is to make the smallest changes possible, and relentlessly test each change. Upgrading a major version tick is a big change, so you must force the upgrade to work incrementally, as a series of small changes.

Phlip Plumlee http://www.oreilly.com/catalog/9780596510657/ I have upgraded several Rails 1.2.x programs to 2.x. This can be quite a leap, and some of the steps are counterintuitive, so this post attempts to put everything together, like a recipe. I'd also like to hear more stories about upgrading platforms; such stories may indeed emend my suggested hacks and tweaks. Yet the point of unit tests, and TDD, is to make the smallest changes possible, and relentlessly test each change. Upgrading a major version tick is a big change, so you must force the upgrade to work incrementally, as a series of small changes. tag:broadcast.oreilly.com,2009://53.35328 2009-02-15T23:33:08Z 2009-02-15T23:33:08Z

All blogs correlate their posts with tags. This blog post shows how to use these tags to display a mind map, hooking the current post into a tree of related posts.

Phlip Plumlee http://www.oreilly.com/catalog/9780596510657/ All blogs correlate their posts with tags. This blog post shows how to use these tags to display a mind map, hooking the current post into a tree of related posts. tag:broadcast.oreilly.com,2008://53.33725 2008-10-09T14:06:20Z 2008-10-09T14:06:20Z

Test Driven Development works best when each test case targets one aspect of a class's interface. So this post will demonstrate a simple and direct way to test a partial without testing the Views, layouts, and Controller actions surrounding it. On very complex projects, this technique keeps your partials decoupled.

Phlip Plumlee http://www.oreilly.com/catalog/9780596510657/ Test Driven Development works best when each test case targets one aspect of a class's interface. So this post will demonstrate a simple and direct way to test a partial without testing the Views, layouts, and Controller actions surrounding it. On very complex projects, this technique keeps your partials decoupled.