Progress Telerik JustMock
Easily Debug Mocked Objects
From finding what arguments your mock object is called with to why it’s not called or why it’s called repeatedly, the JustMock Debug Window helps you find the answers you are looking for while debugging your unit tests.
-
Debug Mocked Objects
Quite often when you write your unit test, the mock object doesn’t work as expected. Sometimes the issue Sometimes the issue is due to a difference between the arguments used for the arrangement and the arguments with which the method was called. Other times the mocked method is called too many times and you don’t know from where and why. In those situations, you need to carefully revise your code and experiment before you find the root cause of the issue. This wondering around is now solved by the JustMock Debug Window. It provides you all the required information you need about the arranged mock, including with what arguments the mocked method was arranged, how many times the mocked method is called, with what arguments and what is the call stack of each call.
All JustMock Components
Mock Everything
- Interfaces
- Virtual and Abstract Methods and Properties
- LINQ Queries
- Sealed Classes
- Static Classes, Methods and Properties
- Non-Virtual Methods and Properties
- Non-Public Members and Types
- Generics
- Delegates
- Entity Framework
- Extension Methods
- MsCorLib Members
- Named Arguments
- Local Functions
- Ref Return Values and Ref Locals
- DLL Imports
- Threadpool
- Microsoft SharePoint
- Supported Languages C#, VB and F#
Mocking and Assert Functionality
- Assert Call Order
- Assert Occurrence
- Future Mocking
- Fluent Mocking
- Partial Mocking
- Sequential Mocking
- Recursive Mocking
- Automocking
Integrate with Testing Frameworks
Build System Integration
Integrate with Other Tools
Next Steps
See Plans & Pricing
Purchase individual products or any of the bundles
Download Free Trial
With dedicated technical support.