Nov 8, 2010
visibility 5020
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
Build Your First Opal Tool in C#

Optimizely ships a C# SDK for building custom

Adnan Zameer | Nov 2, 2026 |

Introducing Publishing Timeline for Optimizely CMS 13

When working with scheduled content in Optimizely CMS, having a clear overview of what's going live and when can be really helpful, especially when...

Mardy | Nov 2, 2026

What else changed in Optimizely CMS 13.5.1

Optimizely CMS 13.5.1 lists a single Graph fix in its release notes. I decompiled the packages and found more: a new setting that lets editors find...

Tomas Hensrud Gulla | Nov 1, 2026 |

New logo and login page in Optimizely CMS 13.5

CMS 13.5.0 quietly ships a new logo and a redesigned login page.

Tomas Hensrud Gulla | Oct 30, 2026 |