{"id":1345,"date":"2011-07-11T15:37:27","date_gmt":"2011-07-11T07:37:27","guid":{"rendered":"http:\/\/www.sharepointboost.com\/blog\/?p=1345"},"modified":"2023-07-31T11:40:56","modified_gmt":"2023-07-31T03:40:56","slug":"rough-explanation-of-test-driven-development-tdd-in-sharepoint","status":"publish","type":"post","link":"https:\/\/www.boostsolutions.com\/blog\/rough-explanation-of-test-driven-development-tdd-in-sharepoint\/","title":{"rendered":"Rough Explanation of Test Driven Development (TDD) in SharePoint"},"content":{"rendered":"

Background:<\/strong>
\nMany teams use XP Agile Development. Test driven development (TDD) is a software development process that relies on the repetition of a very short development cycle.<\/p>\n

Write test code before developing feature will bring a stable and high quality architecture.<\/p>\n

MSTest is a nice unit test framework, and the Nunit is also a good choice.
\nThe following is the unit test sketch map:<\/p>\n

\"\"<\/a><\/a>
\nUnit testing in normal business object:<\/strong>
\nFor OOA, OOD and OOP, programming to an interface is a good approach. Every object is isolated and the interface make a role as relationship between the objects. We can use Dependency Injection with constructor to build relationships between the objects.<\/p>\n

We will introduce other approach such as IOC, AOP and so on in future to improve the quality and efficiency of SharePoint development.<\/p>\n

<\/p>\n

You should use the mock to instead of the object which cost lots of resource.
\nA mock object is a more evolved and recent version of a fake.<\/p>\n

The NMock2 framework is an open-source library providing a dynamic framework for .NET interfaces. The mock object uses strings to get input and reflection to set expectations. You can reference the link: http:\/\/sourceforge.net\/projects\/nmock2<\/a><\/p>\n

The code is as following:<\/p>\n

\/\/ The BLL interface
\nnamespace Landpy.SharePointTest.SystemInterface
\n{
\npublic interface ILandpySettingReader
\n{
\nLandpySetting GetLandpySetting(string url);
\n}
\n}
\n\/\/ The data structure
\nnamespace Landpy.SharePointTest.SystemInterface
\n{
\npublic enum LandpySettingType
\n{
\nNormal,
\nSpecial
\n}
\n}
\nnamespace Landpy.SharePointTest.SystemInterface
\n{
\npublic class LandpySetting
\n{
\npublic LandpySettingType Type
\n{
\nget;
\nprivate set;
\n}<\/p>\n

public LandpySetting(LandpySettingType type)
\n{
\nthis.Type = type;
\n}
\n}
\n}
\n\/\/ The MSTest TestMethod
\nLandpySetting normalLandpySetting = new LandpySetting(LandpySettingType.Normal);
\nLandpySetting specialLandpySetting = new LandpySetting(LandpySettingType.Special);
\nMockery mockery = new Mockery();
\nILandpySettingReader landpySettingReader = mockery.NewMock<ILandpySettingReader>();
\nExpect.Once.On(landpySettingReader).Method(“GetLandpySetting”).With(“http:\/\/landpy.cn”).Will(Return.Value(normalLandpySetting<\/a>));
\nExpect.Once.On(landpySettingReader).Method(“GetLandpySetting”).With(“http:\/\/landpy.com”).Will(Return.Value(specialLandpySetting<\/a>));
\nAssert.AreEqual<LandpySettingType>(landpySettingReader.GetLandpySetting(“http:\/\/landpy.cn”).Type<\/a>, normalLandpySetting.Type);
\nAssert.AreEqual<LandpySettingType>(landpySettingReader.GetLandpySetting(“http:\/\/landpy.com”).Type<\/a>, specialLandpySetting.Type);<\/p>\n

You can see that there is no implement about the interface, the mock object is visual object and it can instead of the object which cost lots of resource.<\/p>\n

Unit testing in SharePoint object:<\/strong>
\nWhat is the difficulty of SharePoint unit test? We need to mock the SharePoint object such as: SPSite, SPList and so on.<\/p>\n

Program to an interface in the business logic layer(BLL), we use mock technique to invoke the fake object to instead of the SharePoint object model.<\/p>\n

You can use SharePoint TypeMock Wrapper to mock the SharePoint object model. Just a pity, the TypeMock is not free.<\/p>\n

The codeplex official code is as following:<\/p>\n

MockSPSite mockSite = new MockSPSite(“TestSite”); MockSPWeb mockWeb = new MockSPWeb(“TestWeb”);
\nMockSPList mockList0 = new MockSPList(“MyList0”);
\nMockSPList mockList1 = new MockSPList(“MyList1”);
\nMockSPList mockList2 = new MockSPList(“MyList2”);
\nmockWeb.Lists = new MockSPListCollection(new[] { mockList0, mockList1, mockList2 });
\nmockSite.Mock.ExpectGetAlways(“RootWeb”, mockWeb.GetInstance());
\nSPWeb WebMocked = mockWeb.GetInstance();
\nusing (RecordExpectations recorder = RecorderManager.StartRecording())
\n{
\nSPSite SiteMocked = new SPSite(“”);
\nrecorder.ExpectAndReturn(SiteMocked.OpenWeb(), WebMocked);
\n}
\n<\/strong><\/p>\n

Mock Framework:<\/strong><\/p>\n