Nicklas Israelsson
Mar 7, 2014
visibility 6791
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
Optimizely Graph - Provisioning, User Management & Developer Instances

Upgrading to Optimizely CMS 13 marks a major architectural shift as Optimizely Graph takes over as the central query and delivery engine, retiring...

Scott Reed | Sep 28, 2026

An (unofficial) MCP server for Optimizely Data Platform (ODP)

I wanted to ask Claude some questions about session setup data in Optimizely Data Platform (ODP) without writing GraphQL every time. There's no...

Jacob Pretorius | Sep 28, 2026

Admin UI for Optimizely SaaS CMS Integrations Without Extra Tools: Preview-Based Dashboards, OCP UI Extensions and Keeping Them Private

On PaaS we extended the CMS UI with custom admin panels; SaaS CMS has no such hooks. Here is a workaround: an admin UI for external content...

Szymon Uryga | Sep 27, 2026 |

Personalisation in CMS 13 when you go headless: variations in the CMS, decisions in Experimentation

Back in February I wrote about personalisation in CMS 13 using Audiences . Everything in that post still holds, with one condition I should have ma...

Minesh Shah (Netcel) | Sep 24, 2026