Ninject.MockingKernel | Extension for Ninject aiding testability in Moq | Testing library

The above approach/design is going to cause all manner of head aches to maintain/test as the controller is tightly coupled to the kernel (IoC container) which basically does not allow one to be able to easily mock/replace it for testing.

Also note that the examples linked in question all have in common the ability to explicitly inject the dependencies into their subjects under test.

The above is basically using the kernel as a service locator.

Trying to put lipstick on that code may change its appearance but does nothing about the smell.

Ideally the design should be following the explicit dependency principle.

Methods and classes should explicitly require (typically through method parameters or constructor parameters) any collaborating objects they need in order to function correctly.