Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations Known Issues And Limitations

Known Issues And Limitations

Top  Previous  Next

Requirements for projects under test

(your production code that you'd like to test)

 

 

·Your project under test must be compiled to produce debugging information:
·MSsymbol On Windows: Compile in DEBUG and to export PDB to be able to be tested.
·linuxsymbol On Linux: Follow the instruction in Configure Test Code for Isolator++ Professional.
·To fake Global C Methods, your project under test requires RTTI.
·The code under test needs to be in a dynamic/shared or a static library, or tests need to be part of the production code

 

Unsupported types (cannot be currently faked)

all classes under the following namespaces are not currently supported for faking:

 

·std
·stdext
·boost

Copyright  Typemock Ltd. 2009-2021.  All Rights Reserved.