Channels ▼
RSS

Database

Typemock Isolator++ Goes 64 Bit


Typemock's Isolator++ unit testing solution now supports both 32- and 64-bit C/C++ code written on Windows, including legacy code not originally written to be tested.

The Isolator++ "mocking framework" uses macros in order to change the behavior of methods under test. It also enables asserting method calls and parameters on dependencies when it is not possible to test for return values and/or state change.

As Typemock correctly points out in the case of C/C++ systems, testing means running tests on the entire bulk of code, which would incur prohibitive costs. In addition, setting up tests is complex and slow since they run on the database and there are always high risks of introducing new bugs to the system when changing the code, as there are no good re-factoring tools for C/C++.

Many functions in C/C++ don't just return values, but also use parameters that are passed by reference to return values. Isolator++ can mock the functions and simulate returning values by reference, as if the code actually ran and returned them.

This tool integrates with three coverage tools: AQTime, SoftwareVerify, and BullsEye coverage, and it is compatible with all testing frameworks and all continuous integration tools.

"Programmers can choose to work with either the 32- or 64-bit library depending on their code. This release is game changer for companies with C/C++ code", said Eli Lopian, founder of Typemock.

"Many established enterprises have software that was written in C/C++ specifically due to its stability and robustness. We see large companies in highly-regulated industries (such as banking, insurance, medical, automotive, and defense) that run into serious quality and budget issues when they need to introduce changes into their existing software. For these companies, throwing away old code and writing new code is not a viable option. The code must be tested and mocked, and Isolator++ is currently the only framework that can do it."


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video