We provide tools that help you test and debug the software that you develop.
You can also automate their usage for use in your unit tests, smoke tests and regression tests.
We help you to find and fix bugs faster, and more reliably.
Our goal is to make you more productive and successful.
Are you tired of tools that collect lots of valuable data but then don’t allow you to inspect that data thoroughly?
Just looking at the problem (or the data) in a different way can let you see the problem differently. The “Eureka!” moment.
Following this philosophy, we’ve created tools that provide multiple ways of inspecting and querying your data, allowing you to understand aspects of your software that were previously unavailable to you.
Modern software engineering practices mean that many technologies are in use. Compiled software (native) and just-in-time compiled software (.Net) are used for many applications. Some applications use both technologies. Whichever way you develop, we have tools that support those technologies.
.Net Services are supported.
Native Services are supported with the Software Verify Service API.
ASP.NET is supported.
ISAPI DLLs are supported with the Software Verify Service API.
For an interactive exploration of the collected data, we provide multiple user interfaces to show different perspectives on the data.
Most user interfaces support context menus to allow you to filter the data, or change the perspective by displaying the data on another view.
If you like to run automated tests, unit tests, regression tests, smoke tests etc., we have a command line that allows you to automate our software tools.
Don’t like writing command lines? We have that covered too.
Find any already launched program on the launch dialog, select it, the command line builder will automatically create your command line for you.
You don’t need to use our API for most things, but if you choose to do so, you can fit it and forget it.
If your software using the API is installed on a computer without the Validator (for example, a customer machine) the API will do nothing.
This allows you to ship your development code with the API installed because it won’t do anything unless your software has been started from the Validator.
Only native services and IIS ISAPI need to use the API. For everything else, API use is optional.
We support your compiler / IDE, and support all Windows operating systems all the way back to Windows XP, including Windows Embedded.
We think software tools should concentrate on one job at a time. Your memory leak tool should be all about memory issues – it shouldn’t be trying to be a performance profiler and a deadlock detector at the same time.
The right tool for each job.
If you develop for Windows and use Visual Studio, C++ Builder, Delphi, QtCreator, MingW we have tools to help you. They can help you to find and fix bugs in C, C++, Delphi, Fortran, Visual Basic, C# and VB.Net.
We’ve helped thousands of software developers find, fix, and prevent bugs.
For 21 years we’ve been providing tools to tackle the biggest problems out there: our happy customers include giants like Adobe, Cisco, Intel, UBS, and HP.
The problem I needed an easy way to automate the building of a Visual Studio project from the command line. It needed to work regardless […]
Everything written here applies to all Validators: Bug, Coverage, Memory, Performance and Thread. There are many ways to start collecting data with a Validator: Launch, […]
Bugs are an unfortunate part of being a software developer. Sooner or later you’re going to bump into one and need to ask the vendor […]
In this article I’m going to explain how we provide customer support. Free Customer support is free. There is no charge for customer support. Customer […]
Minidumps can be really useful for creating a self-contained record of a crash for analysis later, either by your own software team, by a consultant, […]