herodb | A simple key/value store backed by git | Key Value Database library

First of all let's set the basis first: unit testing is different than integration testing.

In that case this is a unit test on the controller's method ContactStatusList. You're testing only this method and you actually did things correctly by trying to mock your HeroDb object. Note that you decided to mock this object because this is a dependency.

The problem is you set up the Mock but you don't use it because in your ContactStatusList method you call new DBClass.HeroDb().

There's a 2nd problem is that you're trying to mock a class. This is actually possible but all the class's methods you want to mock must be declared as virtual. Therefore it's actually better to mock an interface instead.

This interface should be received in the constructor of your ListController. On a regular execution of your Web Project inject an instance of that interface in the startup but in unit tests feed your mock to the ListController's constructor.

Remember this rule: Any dependency should be received by your controller's constructor

Here is your interface and your DbHero class