Nov 8, 2010
  4694
(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
Meet the latest OMVPs - H1 2026 Cohort

Meet the Latest Cohort of Optimizely Most Valuable Professionals (OMVPs) Every year, the Optimizely Most Valuable Professional (OMVP) program...

Satata Satez | Mar 13, 2026

Optimizely Commerce vs Composable Commerce: What Should You Do with CMS 13?

As organizations modernize their digital experience platforms, a common architectural question emerges: Should we continue using Optimizely Commerc...

Aniket | Mar 12, 2026

Missing Properties tool for Optimizely CMS

If you have been working with Optimizely CMS for a while you have probably accumulated some technical debt in your property definitions. When you...

Per Nergård (MVP) | Mar 10, 2026

AI Generated Optimizely Developer Newsletter

Updates in the Optimizely ecosystem are everywhere: blog posts, forums, release notes, NuGet packages, and documentation changes. This newsletter...

Allan Thraen | Mar 10, 2026 |