{"id":305,"date":"2011-03-10T21:49:05","date_gmt":"2011-03-10T21:49:05","guid":{"rendered":"http:\/\/www.myfatblog.co.uk\/?p=305"},"modified":"2011-03-11T08:28:36","modified_gmt":"2011-03-11T08:28:36","slug":"part-3sharepoint-retreattdd-and-unit-testing-the-methodology-used-cont","status":"publish","type":"post","link":"http:\/\/www.myfatblog.co.uk\/index.php\/2011\/03\/part-3sharepoint-retreattdd-and-unit-testing-the-methodology-used-cont\/","title":{"rendered":"Part 3–SharePoint Retreat–TDD and Unit testing, the methodology used cont.."},"content":{"rendered":"

The other parts of this series can be found here\u00e2\u20ac\u00a6<\/p>\n

    \n
  1. SPRetreat TDD \u00e2\u20ac\u201c a retrospective (See what I did there? -)<\/a> <\/li>\n
  2. Part 1 \u00e2\u20ac\u201d SharePoint Retreat\u00e2\u20ac\u201cTDD and Unit Testing, the methodology used<\/a> <\/li>\n
  3. Part 2 — SharePoint Retreat\u00e2\u20ac\u201cTDD and Unit Testing, the methodology used cont..<\/a> <\/li>\n
  4. Part 3 -\u00e2\u20ac\u201c SharePoint Retreat-TDD and Unit Testing, the methodology used cont..  (This post) <\/li>\n<\/ol>\n

    Moving into the realms of SharePoint<\/h2>\n

    In the previous episode, we created our Magic8Ball object using TDD techniques to drive the creation of the Objects, Properties, Fields and methods. We now need to take that completed object and look at how we bring it into the SharePoint environment, utilising TDD whre possible. (Note: I\u00e2\u20ac\u2122m focussing on TDD here, not SharePoint, therefore this is NOT production standard code.<\/em>)<\/p>\n

    We didn\u00e2\u20ac\u2122t get quite as far as getting our Magic8Balls fully into SharePoint on the retreat, other than to use TypeMock to isolate us from calls to the object model. Therefore this part will hopefully generate a bit of retrospective discussion as I\u00e2\u20ac\u2122m going to try and adapt what I learnt about TDD on the Retreat and apply it here, without the benefit of the retrospectives we held.<\/p>\n

    If I get this wrong, it will in any case reinforce the need to hold Agile retrospectives when possible! \"Winking<\/p>\n

    The important thing to remember is that we don\u00e2\u20ac\u2122t need to use TDD on everything in this project. We\u00e2\u20ac\u2122re going to use the supplied distribution framework from MS for instance, and one hopes that they\u00e2\u20ac\u2122ve tested this thoroughly, therefore we won\u00e2\u20ac\u2122t.. Crossing the Seams\u00e2\u20ac\u00a6 remember?\"image\"<\/a><\/p>\n

    In order to help this process, I\u00e2\u20ac\u2122m going to create a new SharePoint aware class that inherits from Magic8Ball. I can then use this class simply in a Sharepoint web part project, keeping the logic and display separation as much as possible. We\u00e2\u20ac\u2122ll add the corresponding test class to the test project at the same time.<\/p>\n

    Remember to decorate your test class with the TestFixture attribute so that NUnit knows it has tests in it. Let Resharper handle the Using statements for you, it\u00e2\u20ac\u2122s quicker!<\/p>\n

    \"image\"<\/a><\/p>\n

    At this point, I forgot to make the SharePoint8Ball class public, but Resharper spotted that and offers to fix it..<\/p>\n

    \"image\"<\/a><\/p>\n

    We\u00e2\u20ac\u2122ve allowed Resharper to do this and we can now reference the class in our test code.<\/p>\n

                SharePoint8Ball spball = new<\/span> SharePoint8Ball();\r\n            spball.Answers = new<\/span> List<string<\/span>>() {"a"<\/span>, "b"<\/span>, "c"<\/span>};<\/pre>\n