FakePointA set of fake (mock or stub) SharePoint object model API classes | |
Download |
FakePoint Ranking & Summary
Advertisement
FakePoint Tags
- Object Model model SharePoint API mock SharePoint Object Model database object model API API set RMI Stub compiler RMI stub Component Object Model Domain Model API atom object model stub Mock Object Creator generate Mock Object Mock Object maker Mock Object stub objects generator C++ object model create object model Text Object Model comprise classes set inject mock object XML Infoset object model model CIM object Adaptive Object Model SharePoint object model API API class object model explorer SharePoint Server object model Mock Framework mock creator create mock outlook object model security g pay stub template word object model
FakePoint Description
The FakePoint package provides a set of fake (mock or stub) SharePoint object model API classes to enable unit testing and TDD. The FakePoint DLL is referenced in the test project in place of the SharePoint assembly, allowing the fake API classes to be used transparently without special coding. Unit testing is very difficult with SharePoint. Much SharePoint development is involved with the user interface, which is notoriously difficult to unit test. But an even worse problem is that the SharePoint object model API is large and complex, and interactions with SharePoint objects often comprise the majority of the coding in a SharePoint development project. The common solutions are either to use a mocking framework, or to radically modify the solution architecture to create an abstraction layer around SharePoint. Currently the only framework that can be used to emulate the SharePoint API is TypeMock Isolator, which is excellent, but is a commercial product. The architectural wrapping approach usually results in a complex dependency injection pattern, or in unit tests that are "protected" from the critical sections of code. Unit testing is so difficult that in many SharePoint development projects the developers are obliged to go straight to integration style testing against a local instance of SharePoint. This introduces enormous configuration dependencies into the tests, and makes the test cycle slow enough to hamper development and debugging and prevents the adoption of test-driven development (TDD). FakePoint gives you an alternative to mocking and re-architecting that allows you to replace the SharePoint API with a set of fake classes. Rather than setting up a response for each API call prior to running the test, an entire fake SharePoint site is created, complete with content. Once this fake site is set up, any number of tests can be run against it. This makes test setup very simple and also removes the need to predict what the API response would be to a particular call in order to set up the response conditions.
FakePoint Related Software