Mattias Lövström
Aug 26, 2010
visibility 6141
star star star star star
(0 votes)

TDD for your custom page providers

I have created a project for developing page providers with test driven development, and my idée is that it should be great if we have an open source project where many EPiServer developers can contribute so the developing of custom page providers gets easier.

So please sign-up to be a contributor of this project, by sending me a CodePlex message.

My first version of the project includes 43 integration tests and is testing the version handling of PageData objects based on the earlier blog I wrote Version state graph of a PageData object. Those tests uses an own MemoryPageProvider (original written by Johan Björnfot) and doesn’t requires any EPiServer database. This page provider are only changed so it fulfills the requirements in the test cases, but I hope in the end it should be a really good example for writing a custom page provider that has similar functionality as EPiServers local page provider.

Requirements:

- EPiserver CMS 6

- MS Test (or NUnit)

Download source:

PageProviderTests for EPiServer CMS on CodePlex

Aug 26, 2010

Comments

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |