ARCast.TV - TDD / MVP with Ron Jacobs

Description

Most of the time I am the host of ARCast but recently I went to New Zealand where Luckas Svoboda hosts ARCast New Zealand www.arcast.co.nz and he wanted to inteview me for their show.  I thought it would be fun to share this episode with you.

The Discussion

  • User profile image
    Mazric
    Ron,

    I am just listening to your Podcast, is there any chance If you could make your source code available, it would be great to see an simple example of PVP with TDD.

    Thanks in Advance

    Maz
  • User profile image
    FireGarden
    yes source code would be great. Good topic of disucssion. Have you ever considered the relationship between MVP patterns and code generation technology?

    I have a feeling in my gut that TDD is a path to code generation.

    R
  • User profile image
    rojacobs
    Yes the source for this application is available at www.ronjacobs.com
  • User profile image
    Mazric
    thanks ron
  • User profile image
    joshnuss
    Thanks Ron. More TDD man!

    Slight Rant:


    It has been written that the TDD methodology requires aprox twice as much test code as application code. Which translates into 2/3 of developer time spent on writing test code. This is where developers are spending most of their time which is a fruitful area for new productivity gains.

    Sometimes, I wish more teams at Microsoft were thinking about TDD. It really sucks to try and acheive 100% code coverage over an API that doesnt use interfaces (i.e. HttpContext, HttpRequest, HttpResponse..).

    True, progress has been made:D. Newer projects like ASP.NET MVC[H] do emphasize unit testing in their documentation and project templates. But still others like EDM dont apear to design for this scenario up front.

    More emphasis needs to be placed on designing for testing (as your great tdd videos have demonstrated). Architects & developers need more information up front about how APIs can be tested (best practices etc..). and as a general rule, APIs should have at least one article in their .chm that outlines their API testing story.

    We should do away with all all those "Console.WriteLine" style examples to and replace them with actual unit tests (asserts, mocks and all).

    Happy Holidays,

    TDD Koolaid Drinker



Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.