You can incorporate Quantify into existing test harnesses, makefiles, and scripts. For example, in a makefile:
hello_world: hello_world.o
cc –g –o hello_world hello_world.o
you can just add quantify
hello_world: hello_world.o
quantify cc –g –o hello_world hello_world.o
or you can create a separate target for the instrumented executable:
hello_world: hello_world.o
cc –g –o hello_world hello_world.o
hello_world.pure: hello_world.o
quantify cc –g –o hello_world.pure hello_world.o
See also the sample makefile located in the <quantifyhome>/example_quantify directory.
View output from your tests using one of the following commands
qv <view file name>
quantify -view <view file name>
Use Quantify command-line options and API functions to control profiling and reporting. For example, the -write-export-file option sends Quantify output to a Quantify export file, and the -logfile option sends Quantify logging output to an ASCII log file. This is convenient when you want to run a set of nightly tests under Quantify, then review the results the following morning.
Use the --run-at-exit and -run-at-save options for automated evaluation of Quantify export files. For information about using Quantify scripts to automate the analysis of this data, read Automating data analysis.
To make sure that the run-time options you specify remain in effect whenever the executable is run, use the -ignore-run-time-environment option.
To output Quantify version information, use the -version option.