The following options let you control the sessions during testing
Allows a previously created session to be loaded into Performance Validator to act as the baseline session against which other sessions are compared.
-baseline c:\baselineRegTests\testMacro1.pvm
-baseline "c:\baseline regression tests\testMacro1.pvm"
Sets the number of sessions that can be loaded at once.
This is equivalent to the same setting in the session manager and can't be less than 1.
Example:
-numSessions 2
Saves the session data when all data has finished being collecting from the target program.
Performance Validator 32 and 64 bit use the file extension .pvm and .pvm_64 respectively.
A missing or incorrect filename extension will be corrected automatically
Examples:
-saveSession c:\results\testMacro1.pvm
-saveSession "c:\test results\testMacro1.pvm_x64"
-saveSession c:\results\testMacro1
Loads a previously created session to be compared with the performance data from the session being recorded.
These options might be used when a series of tests have already been performed and their sessions saved.
Performance Validator 32 and 64 bit use the file extension .pvm and .pvm_64 respectively.
A missing or incorrect filename extension will be corrected automatically
Examples:
-sessionLoad c:\results\testMacro1.pvm
-sessionLoad "c:\test results\testMacro1.pvm"
-sessionLoad c:\results\testMacro1
Ensure your session manager is configured to hold at least 2 or 3 sessions or use -numSessions to specify how many sessions to use.
-sessionCompareHTML
-sessionCompareXML
Compare two sessions, producing an HTML or XML report detailing any performance regression and improvements.
The topic on exporting sessions has a description of the XML tags.
The two sessions can be loaded using one of these options:
-baseline and -sessionLoad
-baseline and running a program using one of -program, -injectName, -injectID, or -waitName
Examples:
-sessionCompareXML c:\regtests\testMacro1.xml
-sessionCompareHTML "c:\reg tests\testMacro1.html"
Ensure your session manager is configured to hold at least 2 sessions or use -numSessions to specify how many sessions to use.
-compareByParentTime
-compareByTotalTime
During session comparison these options indicate whether to use the percentage of the parent's execution time or the total time as the comparator.
There are no arguments to these options.
Set the percentage threshold to be used when performing session comparisons.
Differences in percentage less than the threshold will be ignored and will not be considered a difference.
The argument is a floating pointer number, and if not specified will default to 1%.
Examples:
-thresholdPC 1
-thresholdPC 1.0000
-thresholdPC 2.5
-thresholdPC 0.0005