Postal is failing in Unit Tests

[andrewdavey]

Postal is failing in Unit Tests

[andrewdavey]

The view engine infrastructure that Postal uses is very tied to ASP.NET. So running outside of this context is always going to cause problems.

Options available:

1- Switch to using Postal's FileSystemRazorViewEngine

var engines = new ViewEngineCollection();
engines.Add(new FileSystemRazorViewEngine(viewsPath));
var service = new EmailService(engines);
service.Send(myEmail);

This uses the RazorEngine library, which hasn't always provided support for all of Razor's features, but may be enough for your needs.

2- Don't test the rendering of the email views in a unit test. Instead mock and verify Postal's IEmailService.Send method.

var emailService = new Mock<IEmailService>();
dynamic email = null;
emailService.Setup(s=>s.Send(It.IsAny<Email>())).Callback<Email>(e => email = e);
// pass the emailService to your RegistrationOrchestrator
// call TrySendEmail...
// then assert things about he email object.
Asset.Equal("example", email.Subject);

[dotnetchris]

Thanks for the update on this Andrew, going with the verified call to Send should be good enough from my specification level, i have an integration test that i can use for rendering the email. I was just wondering if there was a simple fix here.

I might try the filesystem engine but I'm extremely hesitant to adding view engines, i'm using a custom view engine and i always have fear of apocalypse from adding another view engine and that some of my expectations in my custom view engine causes chaos with it.

[dotnetchris]

Switched from using new Email().Send() to taking an explicit dependency to IEmailService and the peasants rejoice.