Nov 8, 2010
visibility 4878
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
Copies vs. Connections: Modeling Content Areas for Multilingual Success

Starting With the Simple Question Most multilingual content modeling conversations start with a deceptively simple question from a client: "If we s...

Vipin Banka | Aug 23, 2026

Content Transfer coming to Optimizely SaaS CMS

Back in June I released Content Transfer on the Optimizely nuget feed – today I’m releasing version 1.0 , because we’ve had it running out in the...

Matt Pallatt | Aug 23, 2026

Improving Optimizely Product Information in LLM Tools

Tools like Claude Code can be great for working with Optimizely CMS, but when they index outdated or incomplete information about developing a...

Nicholas Sideras | Aug 21, 2026 |

How to Get a Bacpac Out of DXP (And Never Do It By Hand Again)

Every Optimizely DXP project eventually runs into the same task: getting production data onto a local machine so you can actually troubleshoot...

KennyG | Aug 20, 2026