How We Made Isolator Even *More* Awesome in 2013
I don’t usually write summary posts.
But when I do, it usually means a year is coming to an end.
Typemock came a long way this year. It always starts with experienced energetic people joining the team. In addition, we’ve changed our perspective a bit about how unit testing helps developers and organizations. Before we wanted to help every developer write tests easily. Now, we want to make the whole unit testing experience easier and accessible.
What’s the difference?
Unit testing is not just writing tests. Sure, this is the starting point, and Isolator started exactly there: mocking. We then added test writing assistance with Intellitest, (test auto-completion) and Test Lint, the test writing guide. Then we added support for running test the right way – separating between fast and slow tests, for quicker feedback – with SmartRunner.
Debugging failed tests is where the value of unit testing is. But then, it’s less about the test itself, and more about code that changed and broke it. We got that information on the methods, so you’ll see everything you need in one place.
Unit testing is also about the integration with your team and tools, and we’ve made easy integration a main product feature since the beginning.
And since unit testing is big, so are the set of features we added to Isolator.
As an example, lets look at what we’ve added to it this year.
- We’ve added the SmartRunner back in version 7. This year, we’ve started adding more stuff around it. It became better and stronger. We’ve put a lot of effort into quick feedback.
- We’ve improved usability. For example, we’ve added keyboard shortcuts to control the SmartRunner and different windows.
- Based on user feedback, we’ve added support running more types of tests, like MSTest ones with deployment items.
- The new Test Navigation Window replaced the hanging (sometimes blocking) dashboard, and you can see not just a solution wide status, but all the tests, divided to groups, where data is more approachable.
- Better visual coverage that shows where each test passes through the code:
- We’ve added plug and play with VS 2012, and OpenCover, and then all coverage tools.
- We’ve added TFS 2012 support with a template, guidance all out of the box.
And we’ve got more good stuff coming in 2014. Here’s a preview (pun intended):
Almost forgot: Isolator’s mocking framework is near perfect. Yet we’ve managed to add to it a couple of APIs this year:
- NonPublic.WhenCalled(…).AssignRefOut – for simulating returning objects by reference
- Fake.NextInstance and Fake.AllInstances (also for interfaces) – a better, simpler API, with complete control over constructors and base constructors
- GetTimesCalled – for asserting the number a method was called
- Abilty to mock DateTime.Today
- IgnoreCall on non-public methods returning values, for clarity.
We’ve got all kinds of terrific stuff coming in 2014 (yes, including support for VS 2013), but until then, if you find mocking intriguing, why not try it out for yourself?
Yes! Give me my FREE Trial of Typemock Isolator Complete!