...
| Table of Content Zone | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||
|
| No Format |
|---|
java -jar selenic_analyzer.jar -encodepass myPassword |
-help
This option prints the list of supported arguments to the console.
-machineId
This option prints the machine ID to the console. Parasoft requires the machine ID to issue a local license. See Licensing.
-maxSessionDaysToAnalyze <value>
This option indicates how many days worth of test sessions to include when analyzing recorded data to generate recommendations. By default, there is no limit, so Selenic will analyze all available recorded data.
In the following example, the Selenic analyzer will use 12 days worth of recorded data to generate locator or wait condition recommendations.
| Code Block | ||
|---|---|---|
| ||
java -jar selenic_analyzer.jar -maxSessionDaysToAnalyze 12 |
The number of days refers to the most recent days for which data was recorded, regardless of how many calendar days have passed.
-performanceBenchmarking
This option enables performance benchmarkingSelenic to calculate and report test execution performance benchmarks. Selenic collects and includes reports test method execution times in the report. The performance benchmarking functionality , and when this option is enabled Selenic calculates the average execution duration per test method based on a minimum set of test runs. Test methods that exceed the average duration by a specified percentage are flagged in the report. Only runs for passing tests are included in the calculation when determining the average.
The minimum number of test runs required to determine the average, as well as the threshold for exceeding the average duration are configurable. See -performanceBenchmarkingMinRuns and -performanceBenchmarkingPercent for information about configuring the performance benchmarking parameters.
This option is disabled by default.
In the following example, performance benchmarking is enabled, the -performanceBenchmarkingMinRuns option is set to 5, and the -performanceBenchmarkingPercent option is set to 20.
| Code Block | ||
|---|---|---|
| ||
java -jar selenic_analyzer.jar -performanceBenchmarking -performanceBenchmarkingMinRuns 5 -performanceBenchmarkingPercent 20 |
After five test runs, Selenic determines that a test method averages 20 seconds to complete. On the sixth run, the test takes 24.2 seconds to complete, which is 21% over the average. The test will be flagged in the HTML report. See Viewing the Report for information about how performance benchmarking is reported.
-performanceBenchmarkingMinRuns <number_of_runs>
This option sets the minimum number of test runs required for test methods that exceed the percentage set with the -performanceBenchmarkingPercent option to be flagged in the report. The average test duration serves as the baseline for the performance benchmarking functionality. See -performanceBenchmarking for details about the performance benchmarking functionality.
Default is 5
-performanceBenchmarkingPercent <percent_threshold>
This option sets the test execution duration threshold for the current test run against the average execution time. If tests in the current run exceed the average test duration by more than the specified percentage, tests will be flagged in the HTML report. See -performanceBenchmarking for details about the performance benchmarking functionality.
Default is 20
-publish
Use this option to publish test results to your project in DTP. The DTP connection and project settings must be configured (see Reporting Results to DTP).
-report <path_to_filename>
This option specifies the location and name of the report file to be generated.
Absolute paths to a directory/file are supported.
Examples:
| No Format |
|---|
java -jar selenic_analyzer.jar -report /home/reports |
| No Format |
|---|
java -jar selenic_analyzer.jar -report "C:\reports\my-report.html" |
The following location is used by default:
"{WORKING_DIR}/report.html"
-sessionId <value>
This option enables you to specify the ID of the test session that contains the recorded data to process. If not specified, the data from the last recorded session is used.
-settings <location_of_properties_file>
Use this option to specify a .properties configuration file containing the execution options for the selenic_analyzer.jar. The .properties file contains licensing and reporting configurations that can be implemented during Selenic analysis. Refer to the following sections for additional information:
-source <directory_or_file>
This option enables you to specify the location of source files or a directory containing source files you want to publish to DTP. You can use multiple -source flags to specify a set of directories or files. This option has no effect if Selenic is not configured to publish sources to DTP (see Publishing Source Files to DTP).
Default is the current working directory.
Example:
| Code Block | ||
|---|---|---|
| ||
java -jar selenic_analyzer.jar -source C:\my_project1 -source C:\my_project2 |
-surefire <path_to_file>
This option enables you to specify the location of the Surefire XML report. The Surefire XML report is created when running tests in Maven and is used to create the HTML report.
Absolute paths to a directory/file are supported.
The following wildcards are also supported:
** - Use two asterisks to match directories.
* - Use a single asterisk to match file names.
Examples:
-surefire "/home/folder"
-surefire "C:\folder\file.xml"
In the following example, Selenic will find XML files in /folder1/folder2/folder3, /folder2/folder3, and /folder3:
-surefire "**/folder3"
In the following example, Selenic will find all XML files prefixed with "ProjectA" in folder3:
-surefire "**/folder3/ProjectA*.xml"
The following location is used by default:
"**/target/surefire-reports/"