Static Code analysis and Testing

Question

We want to implement static code analysis (like SPCop / SPCAF / StyleCop) and unit testing (what's the easiest way to mock SharePoint objects? Are there alternatives to Microsoft Fakes?) into our development process. I want to evaluate some tools that could be integrated into our continuous build.

What are your suggestions, known issues, best practices and most appreciated tools?

It would be nice, if it could detect, e.g., access to lists using the display name (problematic on a non us-en system), SPList.Items.Add vs SPList.AddItem, SPWeb.Lists[] vs SPWeb.GetList (depends on number of lists in the web), usages of SPWeb.AllowUnsafeUpdates, etc.

Thanks in advance!

Answer 1

I've used Telerik's JustMock for mocking up SharePoint objects when unit testing and it works fairly well.

The syntax goes something like this:

SPWeb web = Mock.Create<SPWeb>();
Mock.Arrange(() => web.Url).Returns("http://sharepointsite");

It can be used in conjunction with any Unit testing such as NUnit and VSTest and so on.

Answer 2

The official story is not really a good one. Microsoft built an emulator that enables you to write code that simulates access to a SharePoint server. I have no idea if anyone is using the emulator, I rarely see anything on it.

Here's a session from TechEd 2013 that talks about the emulator: Testing and Debugging Microsoft SharePoint Applications with Microsoft Visual Studio 2012