That’s a slow integration test. Split the methods so that one portion of it returns something, and the second method just takes the result and uses it. This way however, you’ll have to make two calls to your class, which I think is even worse than the previous two options!

Lol, are you going to comment everything!? 😉 I’m making a series of posts with examples like these. About the virtual methods, you’re right.

And about the mock, I’m doing state-based testing here. I know that when writing mocks like these yourself, you can also mark a boolean that some method has been accessed. Timezero update. A mocking framework is even better yet, but I’m trying to keep things as easy as possible. But I’ll add an example with a mocking framework in it as well.

The original idea though, started with someone asking me about how to have mocks and inject those with Unity. So I thought, let’s write some posts on it.