Tag: Test Driven Development

We are open sourcing JustMock Lite and giving it to the community. We are giving you the chance to see and improve upon the JustMock Lite source code and share your changes with others. Now you can easily add any functionality that you need and want. We are sure you can make JustMock Lite even better.

You've heard all of the academic reasons for using a mocking framework. Read about some of the real life reasons to use a mocking framework.

Auto mocking containers are designed to reduce the friction of keeping unit test beds in sync with the code being tested as systems are updated and evolve over time. Read how JustMock helps with automocking.

In typical unit testing scenarios, mocking property getters and setters isn't high on the list of areas of concern. Where it usually comes into play is when an entity’s properties’ values (or the act of setting them) are part of the scaffolding, or behavior for the system under test.

Unit tests are most effective when the System Under Test is isolated from its dependencies.  The best way to isolate your code (and make your code more SOLID) is through dependency injection. But even if you follow the rules of SOLID and inject all of the necessary dependencies in as interfaces, you are still faced with the fact that you depend on them. In order to test your code, something concrete has to be passed into the code in order for it to even compile.  Your production code will most likely use a factory to create concrete instances of the dependent interfaces, but that...