Typemock Blog
typemock.com · Company blog · on HN since 2010
Typemock, a vendor of mocking tools for .NET and C++, blogs about unit testing, legacy code, and its Isolator products.
What HN saysCommenters mostly mention Typemock's Isolator and Isolator++ as ways to mock hard-to-test code, often in posts from people connected to the product.
31HN people shared it
12linked it in comments
83stories submitted
220story points
4 years agolast shared
2010people per year2026
Most-shared posts
- 1Isolator++ (Easy Unit Testing for C++) released4 people · 12 points · first shared 2010 · 5 comments on HN
- 2Homepage4 people · first shared 2011
- 3The importance of unit testing in C++2 people · 8 points · first shared 2011 · 1 comments on HN
- 4Fear and Loathing in Legacy Code2 people · 3 points · first shared 2018 · discussion on HN
- 5The 12 bugs of Christmas1 people · 23 points · first shared 2011 · 3 comments on HN
- 6Reasons to Write Unit Tests1 people · 11 points · first shared 2011 · discussion on HN
- 7Unit-Test Patterns for .NET1 people · 10 points · first shared 2012 · discussion on HN
- 8How to Start Unit Testing .NET Projects: A Unit Testing Guide1 people · 9 points · first shared 2011 · 2 comments on HN
- 9What are the best C++ development tools in Linux?1 people · 8 points · first shared 2011 · 4 comments on HN
- 10Free Chapter of The Art of Unit Testing1 people · 6 points · first shared 2011 · discussion on HN
- 11Let the robot code for you1 people · 6 points · first shared 2012 · discussion on HN
- 128 Commandments for Choosing a Unit Testing Tool1 people · 6 points · first shared 2011 · discussion on HN
- 13Agile Development is Broken1 people · 6 points · first shared 2011 · 1 comments on HN
- 14How to name your first test1 people · 5 points · first shared 2012 · discussion on HN
- 15The Essential Setup To Begin Unit Testing1 people · 5 points · first shared 2011 · 2 comments on HN
What HN people wrote when they linked it
int_19h · 2023-02-11
https://www.typemock.com/ solves this problem.
Also, C# doesn't seal anything by default. The methods are non-virtual by default, but that's a very different thing, and there's a good reason for it when it comes to libraries and versioning.
unitesting24 · 2012-11-21
Love #6 & #7 - Unit Testing and Refactor.
It's such an important practice and best to build the right habits from the beginning. The cost of entry is so low with free mocking frameworks. Even commercial vendors like Typemock got into it with their Basic (http://typemock.com/isolator-product-page)
codereview · 2012-03-18
Testing is a pain and it takes time. Plus, we don't always even find the bugs. But if you write unit tests or want to start unit testing, Typemock's newest release (released last Monday) makes unit testing easy and finds the bugs for you. http://www.typemock.com
fafssaf · 2011-07-13
It's not about unit testing but rather testing properly. With powerful mocking frameworks like Typemock Isolator or Isolator++ http://www.typemock.com many of these issues can be dealt with even for those who don't do TDD
telma1234 · 2011-06-30
Those are great testing frameworks.
Isolator++ is a mocking framework that works with any xTesting framework, such as CxxTest or GoogleTest.
Why don't you download the free trial and tell what you think http://www.typemock.com/isolatorpp-product-page
avih · 2011-02-21
For more information about Isolator, check out http://www.typemock.com. TDD can save startups resources -- performing unit tests will save them money and lead to a better product and thus better reputation.
tjalfi · 2017-05-11
TypeMock Isolator[0] and JustMock[1] can mock nonvirtual methods and static methods. Fody Ionad[2] is a free tool that can replace static methods. The reason that most mocking framework don't support this is that the implementation is complex[3].
[0] https://www.typemock.com/isolator
[1] http://www.telerik.com/products/mocking.aspx
[2] https://github.com/Fody/Ionad
[3] http://mattwarren.org/2014/08/14/how-to-mock-sealed-classes-and-static…
buildops · 2015-09-02
What about Typemock Isolator++ http://www.typemock.com/isolatorpp-product-page
solutionyogi · 2015-03-14
1. This was not written by Joel himself. This was written by a guy named Benji Smith on JoS forum.
2. I understand dependency injection completely but question if it's really required to write quality software OR is it a technique you use because programming languages are lacking.
Let me give you an example. In .NET world, there is a product called, Isolator by a company called TypeMock. It can let you mock any type/method by exploiting CLR.
In .NET, there is a type called System.DateTime with a static property DateTime.Now. I have seen code where people try to write interfaces to inject DateTime.Now. And I think it's an overkill. When I saw their example of how they can mock DateTime.Now without doing DI, I am personally convinced that DI is about addressing limitations of your statically typed language and is not an absolute must.
http://www.typemock.com/TypemockIsolatorExamples
3wetwetw · 2012-02-27
And we're proud of it! It's lazy to do things right first and lazy not to want to fight with our code, seeking out bugs. BTW, Unit Testing is getting even lazier with Typemock Isolator V7 (http://www.typemock.com/isolator-v7). It's finding the bugs for you, so you don't have to waste 2 hours hunting around.
fsafa · 2011-06-07
There are additional examples at http://www.typemock.com/articles
PeterCorless · 2020-02-04
There are tradeoffs with all languages. C++ avoids the GC, but you then have to make sure you know how to avoid the common pitfalls of that language.
We use C++ at Scylla (saw that we got a shout-out in the blog! Woot!) but it's not like there isn't a whole industry about writing blogs avoiding C++ pitfalls.
C++ pitfalls through the years...
• https://www.horstmann.com/cpp/pitfalls.html (1997)
• https://stackoverflow.com/questions/30373/what-c-pitfalls-should-i-avo… (2008)
• http://blog.davidecoppola.com/2013/09/cpp-pitfalls/ (2013)
• https://www.typemock.com/pitfalls-c/ (2018)
I am not saying any of these (Go, Rust, C++, or even Java) are "right" or "wrong" per se, because that determination is situational. Are you trying to optimize for performance, for code safety, for taking advantage of specific OS hooks, or oppositely, to be generically deployable across OSes, or for ease of development? For the devs at Scylla, the core DB code is C++. Some of our drivers and utilities are Golang (like our shard aware driver). There's also a Cassandra Rust driver — it'd be sweet if someone wants to make it shard-aware for Scylla!