Try our software tools for 30 days

The following products are currently available to download for 30 day evaluation:

C++,Delphi,Visual Basic (all tools are 32 bit)
	C++ Coverage Validator Evaluation		C++ Memory Validator Evaluation
	C++ Performance Validator Evaluation		C++ Thread Validator Evaluation
.Net, C#, VB.Net, ASP.Net (all tools support 32 bit and 64 bit .Net)
	.Net Coverage Validator Evaluation		.Net Memory Validator Evaluation
	.Net Performance Validator Evaluation
Java (all tools are 32 bit)
	Java Coverage Validator Evaluation		Java Memory Validator Evaluation
	Java Performance Validator Evaluation		Java Thread Validator Evaluation
Javascript (all tools are 32 bit)
	Javascript Coverage Validator Evaluation		Javascript Memory Validator Evaluation
	Javascript Performance Validator Evaluation
Lua (all tools are 32 bit)
	Lua Coverage Validator Evaluation		Lua Performance Validator Evaluation
Python (all tools are 32 bit)
	Python Coverage Validator Evaluation		Python Memory Validator Evaluation
	Python Performance Validator Evaluation
Ruby (all tools are 32 bit)
	Ruby Coverage Validator Evaluation		Ruby Memory Validator Evaluation
	Ruby Performance Validator Evaluation

What do I get when I download an evaluation version?

Evaluation versions are valid for 30 days from the day the license id was generated (this is usually the day you download the software).

Evaluation versions are fully functional.

Please note that although evaluation versions are fully functional, they cannot be converted into the full product by the use of a special license key, they are a different binary image from the full product.

Bug reporting and bug fixing

We may need your assistance when attempting to reproduce and then fix a bug that you report - we may ask for some or all of the following data (wait for us to ask for it, no need to give us all of this information the first time you contact us).

• Description of bug (or crash report if the bug report is for a crash).
• Description of the operating system, software environment and hardware you are running on (CPU, RAM etc).
• Instructions for reproducing the bug.
• Settings for the software tool you are using (Configure menu, Save Settings option).
• Data session for the session you have recorded (File menu, Save option).
• Demonstration or example application that demonstrates the bug.
• If the bug is with your software application we may need to execute your application to reproduce the bug. In this case we will need the application, any necessary support and data files and debugging symbols if the problem requires symbols.
• If you need an NDA before you can let us test your application, that is not a problem.
• Not all bugs are reproducible and some bugs are not fixable (i.e. they are in 3rd party software, or an Operating System / Hardware problem).

Bugs that require your software to reproduce but for which you are unwilling/unable to supply the software will not be fixed as your software is required to determine the problem.