Roadmap for Q2 2013
In previous Qs we introduced and improved the convenient automocking feature. For Q2 2013 we plan to continue enhancing JustMock by working on computability and integration features as well as API improvements.
Compatibility with third party profilers
If you are developer who uses one of the code coverage tools out there, and you want to use a mocking tool in your tests while checking the coverage of your tests, now you'll be able to do that with JustMock and tools like NCover, dotCover, etc. We will make sure not to create conflicts with other testing tools like NCrunch.
Integration with more build systems
You can run JustMock on a workstation or a build server to make sure that your tests pass every time you create a new build. There are a lot of build servers out there and we will make sure to document our compatibility with some of them including TFS, CruiseControl.NET, Team City, etc.
Unified public API (including mocking of MsCorLib members)
Currently, if you want to mock a MsCorLib member, you have to use syntax that is different from the popular and easy to use JustMock's public API. With the next release you won't have to worry about remembering two different ways to mock with JustMock, you'll use the syntax you know and use the most - the JustMock public API.
We welcome all of your feedback and suggestions. You can request a feature, submit an idea or vote for your favorite items on the Feedback Portal.
Visit the Feedback Portal
DISCLAIMER: We operate in a dynamic environment and things are subject to change - we may decide to add new features at any time depending on our capability to deliver products with "Telerik" quality. The Roadmap only intends to give you some additional information as to what you can expect in future releases.