Fluently testing your Autofac configuration

Given the popularity of the Autofac IoC container, we were surprised that there seemed to be no public library that supported testing your Autofac configuration.

Advanced NCrunch: Isolating tests

I am constantly amazed on how far you can push the frontiers of automated testing in order to reduce blind spots and mitigate software risks.

"dev.talk" or how we started to change the company culture

For the past four months we have a weekly dev.talk about mixed topics. After a colleague of mine and I started to prepare and present these talks for a couple of weeks, we found some colleagues presenting topics as well.

Review: NBP116 – How to Master the Habits of Our Everyday Lives, with Gretchen Rubin

I just love the Internet because it makes expanding your horizon and knowledge increasingly easy for everyone. Each followed link may open up a new door. So let me tell you how i got here:

"dev.talk" or how we cheated our management

After I changed my job, I had to face the same old problem: I have to work for a project. I have to work 40 hours a week and each hour needs to be for a project.

Shipping tests along with production code

With NEdifis we advocate putting tests right beside the code rather than into separate test projects. Both approaches have its pros and cons, yet the more popular still seems to be putting tests into a separate test project, see for example Mark Seemann: Where to put unit tests or StackOverflow: Do you put unit tests in same project or another project? The most common reasons for separated test projects are:

"To throw or not to throw": Asserting exceptions on tasks with async/await

For testing exceptional behaviour i like using FluentAssertions Invoking extensions. However, i noticed that using this with async/await seems not to be supported and requires unelegant rewriting (Please, prove me wrong on this). However, using C# 6 await in try-catch this is now very simple to do: