Nov 8, 2010
visibility 4989
star star star star star
(0 votes)

Testing EPiServer code

One thing I’m known to talk (read: nag) about with my colleagues is (unit) testing and more specifically how it isn’t hard to do.

For instance, take an example from Daniel Berg that’s used to add the very nice to have functionality of fallback language for the xml language files available at his blog here.

If you were to venture a guess, how much would the code change and how much code would be added to write some relevant tests? 

Nov 08, 2010

Comments

Nov 9, 2010 12:37 PM

To start with you would probably want to break the dependency to both HttpContext and PageLanguageSetting. To do so, you would have to write some code to wrap the PageLanguageSetting class in something more abstract. Then have the working class have it´s dependencies on the PageLanguageSetting wrapper class and HttpContextBase instead.

With that done you should be able to start testing.

error Please login to comment.
Latest blogs
Migrating ContentArea.FilteredItems in Optimizely CMS 13

If you have

Adnan Zameer | Oct 19, 2026 |

Categories have landed in Optimizely SaaS CMS: structure, translate, tag and query

Categories arrived in Optimizely SaaS CMS at the end of August, with Graph support alongside. I have wanted a proper taxonomy in SaaS since the fir...

Minesh Shah (Netcel) | Oct 19, 2026

Exploring Cached Templates and Cursor Pagination in the Optimizely Graph C# SDK

While experimenting with the  Optimizely Graph C# SDK (13.3.0) in my local Optimizely CMS 13 Alloy project, I came across two interesting findings:...

Mardy | Oct 19, 2026

EPiServer.ImageLibrary.ImageSharp 2.0.7 delisted from NuGet feed

We have delisted version 2.0.7 of the EPiServer.ImageLibrary.ImageSharp package from the NuGet feed due to a packaging issue. This version was...

Phu Nguyen | Oct 19, 2026