Nov 8, 2010
  4719
(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.

Please login to comment.
Latest blogs
CMS 12 - Optimizely DAM Integration 2.2.0

What's New in Optimizely DAM Integration 2.2.0 Version 2.2.0 of the Optimizely DAM (CMP) integration for CMS 12 is a pretty big release. Many of th...

Robert Svallin | Apr 12, 2026

CMS 13: The New Core Element of Your AI-First Optimizely Platform

CMS 13 is out and already brings solid AI-first foundations. With impressive features already shipped and an exciting roadmap ahead, this is the...

Michał Mitas | Apr 11, 2026 |

Deploying to Linux in SaaS (Configured) Commerce

With Optimizely SaaS (Configured) Commere now suporting net8.0 extensions dll, you will need to make a small tweak to how you distribute you...

Mark Hall | Apr 10, 2026 |

Optimizely CMS 13 and the Alloy demo site

The Alloy demo site now runs on Optimizely CMS 13. Here’s a quick guide to getting it up and running locally.

Tomas Hensrud Gulla | Apr 10, 2026 |