Since last year we've made numerous improvements to the library that strive to make writing unit tests more robust and less error prone. Unfortunately, this tightening often results in broken tests. Such tests were actually broken all this time without you knowing it.
The first exception: Arranging the return value of a constructor call is not supported.
It results from code like this:
Although such code compiles, JustMock has actually never supported arranging the return value of new expressions. You can only override the body of the specified constructor. To prevent errors in tests there's now an explicit check for this mistake. The fix is to simply remove the .Returns() clause from all such arrangements. If the test worked before, it will continue to work when you remove the .Returns() clause, because it has always been tantamount to a no-op.
The other exception: Can not instantiate proxy of class: Could not find a parameterless constructor.
I'm not sure what change in JustMock causes this. Can you show me a short snippet of the test code together with the related class constructors?
I will do everything in my power to make the upgrade as painless as possible for you. I hope this helps.
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.