Brian’s blog entry on A thought on mocking filesystems shows that he understands the point.
One of the potential risks with mock-based testing is of simply reproducing the implementation of the Code Under Test, but that only really gets in the way if you can’t change the collaborators you’re mocking. The point of the exercise is to discover the interfaces of collaborating objects from the point of the view of the client, the CUT. This leads to a coding style with small, focussed interfaces which might be implemented by larger classes. Each object gets just what it needs from its neighbours.
Create your own Web 2.0 company.
My new company is Infelino which specializes in rss-based shopping via instant messaging.
I seem to have ended up committed to quite a lot in November. Here goes:
* 2nd, “Story testing with FIT”:http://bcs-oops.org.uk/cgi-bin/view/SPA/StoryTestingWithFIT, BCS SPA Event, London. With Mike Hill
* 18th, “Responsibility-driven development, test-first”:http://www.xpday.net/Xpday2005/ResponsibilityDrivenDev.html. XP Day Benelux, Rotterdam
* 28th, “Getting to know your customer”:http://www.xpday.org/sessions.php#GettingToKnowYourCustomer, XP Day London. With Andy Pols
* 29th, “Before Iteration Zero”:http://www.xpday.org/sessions.php#BeforeIterationZero, XP Day London. With Nat Pryce
* 29th, “Storytelling with FIT”:http://www.xpday.org/sessions.php#FIT, XP Day London. With Mike Hill
So, right now I’m learning a lot about Apple’s Keynote software…
See you there.
or just “vent your frustrations”:http://www.taylorhokanson.com/work/sledge/page3.html
via. “Grady Booch”:http://www-128.ibm.com/developerworks/blogs/dw_blog_comments.jspa?blog=317&entry=96301