Nicklas Israelsson
Mar 7, 2014
visibility 6679
star star star star star
(5 votes)

Introducing EPiCommerce.Integration.Sample

Integration testing a EPiServer Commerce site can be tricky. How would you know how to initialize everything in a way so that your tests behaves similar to how your site behaves?

In an attempt at answering this question for you I’ve created a sample project for integration testing EPiServer Commerce projects. It’s posted on github.com under the MIT-license and you can find it here:

EPiServer Commerce Integration Test Sample

This sample project doesn’t use selenium or any other web driver to test the UI but instead it aims to initialize an EPiServer Commerce site in a test context so that you can test your business logic below your UI layer.

The README for the project should help you get started but I still want to highlight the requirements. EPiServer Commerce requires the Full-Text Search feature to be enabled on your SQL server and you need a version that supports snapshots. The user running the tests also need access to the master database to be able to create databases. I’ve tried isolating most of the database specific code in the Database class so that if you want a different approach on how to reset state between tests you can replace that one class.

Mar 07, 2014

Comments

Petter Klang
Petter Klang Mar 10, 2014 09:41 AM

Sweet!

Mar 10, 2014 06:31 PM

Yes, this is cool!

error Please login to comment.
Latest blogs
Finding Thomas Part 4 - The Intelligence Layer

I've been finding Thomas for four weeks now. Bear with me — we're almost at the full picture. Quick catch-up : Thomas is the returning visitor who...

Ritu Madan | Jul 14, 2026

The Silent Success: When Your Optimizely SaaS CMS Config Push Succeeds with "0" Changes

  Picture this frustratingly common scenario in headless, code-first development with Optimizely SaaS CMS: You’ve defined a brilliant new element,...

Vipin Banka | Jul 13, 2026

Architecting an Enterprise-Grade Development Pipeline in Optimizely SaaS CMS

Most enterprise teams show up to Optimizely SaaS CMS with a clear roadmap for their release pipeline: DEV → QA → Stage → Prod. Four logical...

Vipin Banka | Jul 12, 2026

Bynder DAM Connector for Optimizely SaaS CMS: Improved Metadata Property Synchronization

While working with the Bynder DAM Connector for Optimizely SaaS CMS , one of the key areas I explored was how Bynder asset metadata is synchronized...

Vipin Banka | Jul 11, 2026

Optimizely DXP: Every Supported Culture, One Searchable Page

Quick one for anyone building multi-language sites on Optimizely DXP. I put together a reference tool listing all 806 supported cultures. More...

Adnan Zameer | Jul 10, 2026 |

A day in the life of an Optimizely OMVP: London Meetup 2026

On 2nd July 2026 the Optimizely London Developer Meetup returned to The Lightwell, and the running theme across the evening was less about individu...

Graham Carr | Jul 10, 2026