Hello!

When moving into unit test project you have to copy like Web.Config from your Web project to the unit test App.Config. Make sure that all Mediachase config files and other config files also goes into the Unit test project.

What I´m guessing is that you are missing some Config files and then you may not have initilized the Order context.

/M

We also experienced issues with licensing (especially when you touch some of the meta data parts). Forgot the details but issue was either license issused based on IP or MAC didn't work in unit tests.

Hmm, I have run EpiServer Commerce within a Console Application, Unit test, totally outside the Context of the Commerce IIS web application. I don´t recall any issue except when you forget to copy config files, settings, license files etc or when a context isn´t initilized correctly.

If you want to go more into Unit Test with EpiServer you can take a look on these

http://etf.codeplex.com/

http://tedgustaf.com/blog/2010/8/unit-test-an-episerver-6-website-using-visual-studio-2010-and-mstest/

/M

You need two things.
1 . configs file should be with bin
2. SQL Context is null and you will need to set that. Pseudo code is like this

if sqlcontext is null

Initialize sqlcontext.

I hope this will help and solve the issue.

Regards
/K

For anyone reading this, we've been working on a massive comemrce build and one of the better ways we found to test everythign was instead of trying to get things like the metadata context to workk under test.  We created wrappers for all the big parts of the system. It's not ideal but after you have wrappers fo the main components life gets a lot easer, I wrote about the experience here

How To Unit Test EpiServer Commerce