JustMock users asked and we listened. With the new JustMock R2 2020 release I am presenting you the brand-new Debug Window(beta), API improvements and VS extension optimizations.
Without further ado let me introduce you to the new features and most important fixes.
Debug Window (v.Beta)
In our yearly product survey for 2019 we asked you to chose or suggest features that are important for you or that you want to see in JustMock. With highest priority for all of you was the Visual Studio window for visualizing mocked objects.
This new feature provides a better debugging experience when writing unit tests with JustMock and will help save you time when resolving issues with mocked objects. Through this window you have access to the data JustMock has as to what arrangements are made for which types, with what arguments and what invocations were made that match the arrangements. Please have in mind that this feature is still in beta and it will be further improved. We would love to hear your feedback and learn how you would like it to evolve.
Improved API for Arg Class
We received feedback that there is an ambiguity as to when the Arg and ArgExpr classes should be used. The Arg class is used for argument matching and ArgExpr is used in the subset of argument matching in the context of non-public methods.
This is why we decided to implement a property named Expr in the Arg class that will provide the access to the ArgExpr implementation through an interface. This way it will be more natural to use one class and its properties for argument matching. For backward compatibility the ArgExpr class will remain as it is, with the difference that it will be hidden from the IntelliSense in Visual Studio.
In addition, we have introduced predefined typed properties for the ArgExpr class similar to those already available in the Arg class.
We sped up the loading time of the JustMock Visual Studio Extension to allow you to start unit tests faster. Until now our JustMock extension was divided in two main components, with the second component being load runtime by the first component. That gave us the flexibility to support very old Visual Studio versions. With this newly launched feature, the functionality of both components is combined, providing faster loading time.
We know that many times our clients want to quickly navigate around the JustMock API and find a useful feature that they didn’t know existed or they forgot how it had to be used. This is why we wrote a cheat sheet article with the intention to lower your learning curve. Here is the link if you want to check it. Feel free to contact us if you think anything is missing.
Unit Testing Blazor Components with bUnit and JustMock
A couple of days ago, I wrote a blog post that guides you on how to unit test Blazor components with bUnit and JustMock. It covers the topic of how to setup your project, simple examples and a master-detail scenario. If you are interested in the topic you could check it out.
The R2 2020 release is already available for download in customers’ accounts. If you are new to Telerik JustMock, you can learn more about it via the product page. It comes with a 30-day free trial, giving you some time to explore the capabilities of JustMock.
Be sure to sign up for the Telerik R2 2020 release webinar on Thursday, May 21st at 12:00 PM ET for a deeper look at all the goodness in the release, where our developer experts will go over everything in detail.
Reserve Your Webinar Seat
Feel free to drop us a comment below sharing your thoughts. Or visit our Feedback Portal and let us know if you have any suggestions or if you need any particular features.
You can also check our Release History page for a complete list of the included improvements.