How do you unit test your mods?

[guiskj]

I am learning how to mod Bannerlord and so far things are going rather well. I am using existing mods to help me navigate the C# code since documentation is not available yet.

However, one thing that I have not been able to understand is how to correctly write unit tests for Behaviours, Layers, ViewModels, etc. There is too much context to set for any of my classes to be constructed correctly and I don't see a path to leverage dependency injection to allow me to mock dependencies.

So I am reaching out here to see if anyone has solved this issue for their mods.

Thank you.

 

[lolxd]

right now? you don't.
wait until they put development kit after EA. Modding atm is a cluster**** and you shouldn't mod EA game anyway

 

[Gaktan]

Don't listen to that guy.
The real answer here is that you usually never need to do unit testing when creating mods, that's just overkill. Usually we do unit tests on a very low level, and this is never done at runtime, but rather at compile time (or when submitting if you have a build validation process).

What you should do instead is secure your code with asserts and logs, that are only enabled in Debug for performance reasons.
The reason is that in case the API changes or if you do some massive changes in your code, you should get notified if weird things happen. That's the proper way to code.

 

[reoo]

right now? you don't.
wait until they put development kit after EA. Modding atm is a cluster**** and you shouldn't mod EA game anyway

What does EA stand for ?

 

[Tocan]

Early access