Data Providers

CSV File (csv, mandatory): Specify the CSV file which contains the findings results (MISRA, Coding Style…​)

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

csv_separator(default: ,): Specify the CSV separator, required on CSV import

Result folder(s) (dir, mandatory): Specify the folder(s) containing XML test results files from CANoe.

Test path (testPath, default: Tests): Define test path (for example Test/HIL Test), by default the value is Tests.

Import Traceability Matrix from vTESTstudio? (import_traceability_matrix, default: false): Traceability matrix file (vtc-tso file) can be generated from vTESTstudio. Using the matrix file will automatically link Tests and requirements)

Traceability File (vtc-tso) (traceability_file): Traceability File (vtc-tso)

Textual information to extract (infoList, default: LIFECYCLE_STATUS?property=TestCase_Lifecycle&map=[Draft:draft]): To specify the list of textual data to extract from the vTESTstudio properties.

Metric information to extract (metricList, default: TEST_LIFECYCLE_STATUS?property=TestCase_Lifecycle&map=[draft:2,under_review…​): To specify the list of metric data to extract from the vTESTstudio properties.

Import Test Execution Plan from vTESTstudio? (import_test_execution_plan, default: false): Test execution plan (vexecplan file) can be generated from vTESTstudio. Using the test execution plan allows to flag requirements as "planned" and test as "executed"

Test Execution Plan file (vexecplan) (execution_plan_file): Test Execution Plan file (vexecplan)

Reset all "Review" States? (reset_review, default: false): This option reset all "Review" information which have been filled in the GUI. Initialize the review state allows to start a new analysis review from scratch.

Reset all "Overload" States? (reset_overload, default: false): This option reset all "Overload" information which have been filled in the GUI. Initialize the review state allows to start a new analysis review from scratch.

Import variant data? (create_variant, default: false): Variant data can be imported beside the test results. It is possible to get an overview of the tests results per variant. CARREFUL: a variant key must be defined.

Variant key (variant_options): Variant key allows to name the variant according relevant variant property. Key=ECU will list all the variant and name them according the value of the field "ECU".

Advanced options (advanced_options, default: false): Advanced options

File suffix (suff, default: .xml): Provide the suffix of CANoe test results files.

Consider "None" as "Passed" (consider_none_as_passed, default: true): By default, a test case which is stated as "none" (=without real evaluation step) are considered as "Passed".

"Hardware revision" key (sut_mapping_hw_rev, default: Hardware revision): "Hardware revision" key can be found in the node of the CANoe xml results.

"Software revision" key (sut_mapping_sw_rev, default: Software revision): "Software revision" key can be found in the node of the CANoe xml results.

"Boot Loader revision" key (sut_mapping_boot_rev): "Boot Loader revision" key can be found in the node of the CANoe xml results.

Add "Report File Name" to the test execution name (displayReportFileName, default: false): Add "Report File Name" to the test execution name.

Add "Test Unit" to the test execution name (displayTestUnit, default: false): Add "Test Unit" to the test execution name.

Add "Variant" to the test execution name (displayVariant, default: false): Add "Variant" to the test execution name.

Use last execution verdict? (useLastExecution, default: false): This option allows to compile all executions from CANoe into one aggregated run.

Import Test Reassessment (importReassessment, default: true): Use this option to import the reassessment verdict from CANoe. This option is useful for user who overloads the test verdict within CANoe.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

createTests(default: YES): Shoult Test artefacts be created?

Cantata XML results (xml): Specify the path to the XML results file or directory from Cantata 6.2

Regex Files (regexFile, default: .xml): Specify a regular expression to find Cantata xml files

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

CheckStyle results file(s) (xml, mandatory): Point to the XML file or the directory that contains Checkstyle results. Note that the minimum supported version is Checkstyle 5.3.

Regex Files (regexFile, mandatory, default: .xml): Specify a regular expression to find checkstyle files

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Configuration file (configFile): A Checkstyle configuration specifies which modules to plug in and apply to Java source files. Modules are structured in a tree whose root is the Checker module. Specify the absolute path of the configuration file. If no custom configuration file is found, a default configuration will be used (this default configuration is for Checkstyle versions from 8.11).

Source code folder (customDirs): Specify the folder containing the source files to analyse. If you want to analyse all of source repositories specified for the project, select None.

Xmx (xmx, default: 1024m): Maximum amount of memory allocated to the java process launching Checkstyle.

Excluded directory pattern (excludedDirectoryPattern): Java regular expression of directories to exclude from CheckStyle, for example: ^test|generated-sources|.*-report$ or ou ^lib$

defaultConfFile(default: checkstyle_for_squore.xml): If the default configuration file is not checkstyle_for_squore.xml, you can specify its name here. If there is no configuration file defined, then this file will be used.

Configuration file (configFile): A Checkstyle configuration specifies which modules to plug in and apply to Java source files. Modules are structured in a tree whose root is the Checker module. Specify the name of the configuration file only, and the data provider will try to find it in the CheckStyle_auto folder of your custom configuration. If no custom configuration file is found, a default configuration will be used.

Xmx (xmx, default: 1024m): Maximum amount of memory allocated to the java process launching Checkstyle.

XML report (xml, mandatory): Specify the path to the XML report generated by Cobertura (or by a tool able to produce data in this format).

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

CodeNarc results file(s) (xml, mandatory): Point to the XML file or the directory that contains CodeNarc results. Note that the minimum supported version is CodeNarc 0.22.

Regex Files (regexFile, mandatory, default: .xml): Specify a regular expression to find CodeNarc files

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

XML results files (xml, mandatory): Specify the path to the XML results file generated by Codesonar. The minimum version of Codesonar compatible with this data provider is 3.3.

Regex Files (regexFile, mandatory, default: .xml): Specify a regular expression to find CodeSonar files

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Standard Configuration Path (s):

Custom Configurations Path (p):

XML results file (xml, mandatory): Specify the path to the XML file containing Coverity results.

CPPCheck XML results (xml, mandatory): Specify the path to the XML results file or the directory from CPPCheck. Note that the minimum required version of CPPCheck for this data provider is 1.61.

Regex Files (regexFile, mandatory, default: .xml): Specify a regular expression to find CPPCheck files

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Source code folder (dir): Specify the folder containing the source files to analyse. If you want to analyse all of source repositories specified for the project, select None.

Ignore List (ignores): Specify a semi-colon-separated list of source files or source file directories to exclude from the check. For example: "lib/;folder2/". Leave this field empty to deactivate this option and analyse all files with no exception.

Cppcheck addon (addon): to a Cppcheck addon. Will be passed to Cppcheck using the --addon= option.

Source code folder (dir): Specify the folder containing the source files to analyse. If you want to analyse all of source repositories specified for the project, select None.

Cppcheck CERT addon (addon, mandatory): Path to CPPCheck CERT python file.

Ignore List (ignores): Specify a semi-colon-separated list of source files or source file directories to exclude from the check. For example: "lib/;folder2/". Leave this field empty to deactivate this option and analyse all files with no exception.

Source code folder (dir): Specify the folder containing the source files to analyse. If you want to analyse all of source repositories specified for the project, select None

Cppcheck MISRA addon (addon, mandatory): Path to CPPCheck MISRA python file.

Ignore List (ignores): Specify a semi-colon-separated list of source files or source file directories to exclude from the check. For example: "lib/;folder2/". Leave this field empty to deactivate this option and analyse all files with no exception.

Directory which contains the XML results files (results_dir, mandatory): Specify the path to the CPPTest results directory. This data provider is compatible with files exported from CPPTest version 7.2.10.34 and up.

Results file extensions (pattern, mandatory, default: *.xml): Specify the pattern of the results files

Choose Excel or CSV import (import_type, default: excel): Specify if the import is about Excel or CSV.

File or Directory (xls_file, mandatory): Specify the location of the Excel or CSV file or directory containing CPU information.

Sheet Name (xls_sheetname): Specify the name of the Excel sheet that contains the CPU list.

Excel file regular expression (xlsx_file_pattern, default: *.xlsx$): Specify a regular expression to find Excel files, by default it's *.xlsx$

Specify the CSV separator (csv_separator, default: ;): Specify the CSV separator

CSV file regular expression (csv_file_pattern, default: *.csv$): Specify a regular expression to find CSV files, by default it's *.csv$

CPU Column name (xls_key, mandatory): Specify the header name of the column which contains the CPU key.

CPU artefact root path (root_node, default: Resources): Specify the root path in Squore of artefacts extracted from the file.

Grouping Structure (xls_groups): Artifacts can be grouped by contextual elements of the file, separated by ";".

Filtering (xls_filters): Specify the list of Header for filtering

"CPU Loop Time" Column name (cpu_loop_column_name, default: Total Loop Time [ms]): Specify the column name of the CPU Loop Time (Ex: "Total Loop Time [ms]")

"Average Idle Time per loop" Column name (cpu_idle_column_name, default: Average idle Time per loop [ms]): Specify the column name of the Average Idle Time per loop (Ex: "Average idle Time per loop [ms]")

"Worst Case Idle Time per loop" Column name (cpu_worst_column_name, default: Worse case idle Time per loop [ms]): Specify the column name of the Worst Case Idle Time per loop (Ex: "Worse case idle Time per loop [ms]")

Create an output file (createOutput, default: true): Create an output file

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

CSV file (csv, mandatory): Enter the path to the CSV containing the coverage data.

CSV File(s) (csv): Specify the path(s) to your CSV file(s) containing findings. To provide multiple files click on '+'. Each line in the file must use the following format and the file should include the following header:

CSV Separator (separator, default: ;): Specify the CSV Separator used in the CSV file.

CSV Delimiter (delimiter, default: "): CSV Delimiter is used when the separator is used inside a cell value. If a delimiter is used as a char in a cell it has to be doubled.

Artefact Path Separator (pathSeparator, default: /): Specify the character used as a separator in an artefact's path in the input CSV file.

Case-sensitive artefact lookup (pathAreCaseSensitive, default: true): When this option is turned on, artefacts in the CSV file are matched with existing source code artefacts in a case-sensitive manner.

Ignore source file path (ignoreSourceFilePath, default: false): When ignoring source file path it is your responsbility to ensure that file names are unique in the project.

Create missing files (createMissingFile, default: false): Automatically creates the artefacts declared in the CSV file if they do not exist.

Ignore finding if artefact not found (ignoreIfArtefactNotFound, default: true): If a finding can not be attached to any artefact then it is either ignored (checked) or it is attached to the project node instead (unchecked).

Unknown rule ID (unknownRuleId): this option is deprecated and will be removed in a future release. You should not use it anymore.

Measure ID for orphan artifacts count (orphanArteCountId): To save the total count of orphan findings as a metric at application level, specify the ID of the measure to use in your analysis model.

Measure ID for unknown rules count (orphanRulesCountId): this option is deprecated and will be removed in a future release. You should not use it anymore.

Information ID receiving the list of unknown rules IDs (orphanRulesListId): this option is deprecated and will be removed in a future release. You should not use it anymore.

CSV File (csv): Specify the path to the input CSV file containing artefacts, metrics, findings, textual information, links and keys.

Metrics CSV File (metrics): Specify the path to the CSV file containing metrics.

Infos CSV File (infos): Specify the path to the CSV file containing textual information.

Findings CSV File (findings): Specify the path to the CSV file containing findings.

Keys CSV File (keys): Specify the path to the CSV file containing artefact keys.

Links CSV File (links): Specify the path to the CSV file containing links.

Reports artefacts mapping problem as (level, default: info): When an artefact referenced in the CSV file can not be found in the project, reports the problem as an information or as a warning.

inconstantFdgDescr: A list of patterns separated by ; corresponding to inconstant part of finding descriptions.

CSV file (csv, mandatory): Specify the path to the file containing the metrics.

ESLint results file (xml, mandatory): Point to the XML file that contains ESLint results in Checkstyle format.

XML results file (xml, mandatory): Specify the location of the XML file or directory containing FindBugs results. Note that the minimum supported version for FindBugs is 1.3.9, and 3.1.7 to 3.1.12 for SpotBugs.

Regex Files (regexFile, mandatory, default: .xml): Specify a regular expression to find FindBugs xml files

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Classes (class_dir): Specify the folders and/or jar files for your project in classpath format, or point to a text file that contains one folder or jar file per line.

Auxiliary Class path (auxiliarypath): Specify a list of folders and/or jars in classpath format, or specify the path to a text file that contains one folder or jar per line. This information will be passed to FindBugs or SpotBugs via the -auxclasspath parameter.

Memory Allocation (xmx, default: 1024m): Maximum amount of memory allocated to the java process launching FindBugs or SpotBugs.

XML results file (xml, mandatory): Specify the XML file containing FxCop's analysis results. Note that the minimum supported version of FxCop is 1.35.

Directory containing results files (dir, mandatory): Specify the path of the root directory containing the GCov results files.

Results files extension (ext, mandatory, default: *.c.gcov): Specify the file extension of GCov results files.

XML File (xml, mandatory): Specify the XML file which contains the findings results (MISRA, Coding Style…​)

"Issue" mapping definition (issue):

"Rule Id" mapping definition (id_rule):

"Message" mapping definition (message):

"File" mapping definition (file):

"Line" mapping definition (line):

"Justification" mapping definition (justification):

GitHub REST API URL (url, mandatory): The URL used to connect to your GitHub's REST API URL (e.g: https://api.github.com/repos/OWNER/REPO)

GitHub token (token): Specify your GitHub token. This token is used in Bearer authentication type.

Filter query (query, default: state=all): Filter query, see github api documentation for available filters, https://docs.github.com/en/rest/issues/issues. For example to retrieve issues with "bug" and "ui" label and with state open enter the query "state=open&label=bug,ui". The query must be encoded. The "&" for parameter separation does not need to be encoded. Spaces and other characters must be encoded.

Number of queried tickets (max_results, default: -1): Maximum number of queried tickets returned by the query (default is -1, meaning 'retrieve all tickets').

Use a proxy (useProxy, default: false): If Squore is behind a proxy and needs to access the outside, you can configure the different properties by selecting the checkbox.

Host name (proxyHost): Configure the host name (it's the same for http or https protocol). Example: http://my-company-proxy.com

Port (proxyPort): Configure the port (it's the same for http or https protocol). Example: 2892

Proxy User (proxyUser): Configure the user if authentication is required

Proxy User Password (proxyPassword): Configure the user password if authentication is required

Enhancement Pattern (enhancement_def, default: ["enhancement", "code cleanup", "refactoring"]): Specify the pattern applied to define tickets as enhancements. This field accepts a regular expression to match one or more path with a list of possible values.

Defect Pattern (bug_def, default: ["bug", ">bug", "backport"]): Specify the pattern applied to define tickets as defects. This field accepts a regular expression to match one or more path with a list of possible values.

Open Ticket Pattern (todo_def, default: ["status:approved", "status:confirmed", "status:work-in-progress"]): Specify the pattern applied to define tickets as open. This field accepts a regular expression to match one or more column headers or path with a list of possible values.

Grouping Structure (group_def, default: ["docs", "tests", "metrics", "design", "ci", "automation", "packaging", "se…​): Specify the paths for Grouping Structure, separated by ";".

In Development Ticket Pattern (r_d_progress_def, default: ["status:work-in-progress"]): Specify the pattern applied to define tickets as in development. This field accepts a regular expression to match one or more path with a list of possible values.

Fixed Ticket Pattern (v_v_progress_def, default: ["status:verification"]): Specify the pattern applied to define tickets as fixed. This field accepts a regular expression to match one or more path with a list of possible values.

endPoint(default: /issues): The end point most probably "issues", set by default.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Syntax Version (syntax_version, default: 0.0): The current version is 1.0.

Choose file type (import_type, default: excel): Specify if the file is about Excel, CSV, JSON, XML or Text.

Input file(s) (input_file, mandatory): Specify the location of the file or directory containing Excel, CSV, JSON, XML or Text file(s) to parse.

Excel file regular expression (xlsx_file_pattern, default: *.xlsx$): Specify a regular expression to find Excel files.

CSV file regular expression (csv_file_pattern, default: *.csv$): Specify a regular expression to find CSV files.

JSON file regular expression (json_file_pattern, default: *.json$): Specify a regular expression to find JSON files.

XML file regular expression (xml_file_pattern, default: *.xml$): Specify a regular expression to find XML files.

Root path (root_path): Defined the root element to retrieve the list of artifacts in the file, required on JSON or XML import.

Text regex (txt_regex): Define a regular expression that will split the lines of a file. Each group of the expression will correspond to a CSV header. The regular expression must be compatible with Java specifications.

Sheet name (sheetname, mandatory): Sheet name to read data from, required on Excel import.

First Line Data index (initial_row): Specify the line index where the first data are defined.

First Column Data index (initial_column): Specify the column index where the first data are defined.

Specify the CSV separator (csv_separator, default: ;): Specify the CSV separator, required on CSV import.

With header (with_header, default: true): Specify if a CSV or Excel file begin with a header line. By default, it is true.

Artifact filters (filter_list): Artifacts complying with the provided filters are kept.

Artifact type (artefact_type): The artifact type used by Squore Analysis model.

Artifact name (artefact_name): Artifact name as displayed in Squore.

Artifact hierarchy (artefact_hierarchy): To specify the path in Squore of artifacts extracted from the file.

Artifact unique ID (artefact_uid): This is the artifact unique ID, to be used by links, from this Data Provider or another Data Provider. Optional unless you want to use links to these artifacts.

Artifact keys (artefact_keys): Artifact keys to be used to link artifact.

Data to extract (data_list): Three measures types are available:

Computed operation (computed_list): Computed operations can be used in several other operations.

Artifact links (artefact_link): Specify how to create links between this artifact and other artifacts.

Extract other artifacts (extract_artifacts): Extract other artifacts to be linked with the main artifact

Other operation (other_op_list): Currently only the array_data operation is available.

Finding rule (finding_rule): It is used to create findings result.

Artifact binding (finding_art_binding): Two operations are possible to find the artifact of the findings.

Finding message (finding_msg): It is the finding message.

Finding location (finding_loc): It is the finding location.

Inconstant pattern (finding_inconstant_pattern): This field is a list of pattern to exclude string form message. The regular expression must be enclosed in a single quote and separated by a semicolon in command line.

Rules to ignore (finding_ignore_rule): This field is a list of rules to ignore when processing finding. The rule must be enclosed in a single quote and separated by a semicolon in command line.

Artifact path is case-sensitive (path_is_case_sensitive, default: true): This option allows you to search for an artifact path taking into account case or not.

Artifact name is case-sensitive (name_is_case_sensitive, default: true): This option allows you to search for an artifact name taking into account case or not.

Ignore artifact path (ignore_src_file_path, default: false): This option allows you to search for an artifact only by its name.

Global error management (global_error_mgmt): If the data is missing or non-compliant:

Date format (date_format, default: yyyy-MM-dd): Formatting the date to match the given pattern. This pattern can be used for all Date metrics and "format(<DATE_PATTERN>)" operation is no longer required. If format is not specified, the following is used by default: dd-MMM-yyyy .

Log level (logLevel, default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

findings_list: To specify the list of findings to extract from the file.

csv_delimiter(default: false): Define if a CSV String is delimited by a " or '.

prettyXml(default: prettyL): Specify the pretty level to write the output file loaded by Squore, by default it is prettyL.

elementSeparator(default: ;): DEPRECATED Parameter used in previous versions of 23.0.0. Not available on DP Editor.

concatSeparator(default: ,): DEPRECATED Parameter used in previous versions of 23.0.0. Not available on DP Editor.

squore_model: Specify the Squore Model used, this field will be displayed in DP editor.

artefact_type_container: DEPRECATED Parameter used in previous versions of 23.0.0. Not available on DP Editor.

defaultPath(default: Unknown): DEPRECATED Parameter used in previous versions of 23.0.0. Not available on DP Editor.

path_list: DEPRECATED Parameter used in previous versions of 23.0.0. Not available on DP Editor.

info_list: DEPRECATED Parameter used in previous versions of 23.0.0. Not available on DP Editor.

metric_list: DEPRECATED Parameter used in previous versions of 23.0.0. Not available on DP Editor.

date_list: DEPRECATED Parameter used in previous versions of 23.0.0. Not available on DP Editor.

squan_output_dir: The configuration ${squanOutputDirectory} can be used.

XML report (xml, mandatory): Specify the path to the XML report generated by JaCoCo. Note that the folder containing the XML file must also contain JaCoCo's report DTD file, available from http://www.eclemma.org/jacoco/trunk/coverage/report.dtd. XML report files are supported from version 0.6.5.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Jira REST API URL (url, mandatory): The URL used to connect to yout Jira instance's REST API URL (e.g: https://jira.domain.com/rest/api/2)

Authentication (useAccountCredentials, default: NO_CREDENTIALS): Possible values for authentication are

Jira User login (login): Specyfy your Jira User login. The login is used in Basic authentication type.

Jira User password (pwd, mandatory): Specify your Jira User password. The password is used in Basic authentication type. This password can be encoded by the Jira Server so as not to be provided in readable form.

Jira User token (token, mandatory): Specify your Jira User token. This token is used in Bearer authentication type.

JQL Request (jql_request): Specify a JQL request (see JIRA documentation) in order to limit the number of elements sent by the JIRA server.

Number of queried tickets (max_results, mandatory, default: -1): Maximum number of queried tickets returned by the query (default is -1, meaning 'retrieve all tickets').

Additional Fields (additional_fields, default: environment,votes,issuelinks): List additional fields to be exported from Jira.

Use a proxy (useProxy, default: false): If Squore is behind a proxy and needs to access the outside, you can configure the different properties by selecting the checkbox.

Host name (proxyHost): Configure the host name (it's the same for http or https protocol). Example: http://my-company-proxy.com

Port (proxyPort): Configure the port (it's the same for http or https protocol). Example: 2892

Proxy User (proxyUser): Configure the user if authentication is required

Proxy User Password (proxyPassword): Configure the user password if authentication is required

Ticket Name (artefact_name, mandatory, default: ${key}): Specify the pattern used to build the name of the ticket. The name can use any information collected from the JSON file as a parameter.

Grouping Structure (artefact_groups, default: fields/components[0]/name): Specify the paths for Grouping Structure, separated by ";".

Filtering (artefact_filters, default: fields/issuetype/name=(Task|Bug|Improvement|New Feature)): Specify the list of path for filtering

Todo list regex (in_todo_list, default: fields/status/name=.)*: Todo list regex (ticket which fit the regex will be considered as part of the TODO list for the analysis)

JSON Root Path (root_path, default: issues): Specify the root path in the JSON file to retrieve issues.

Ticket ID (artefact_id, default: id): Specify the path to the field containing the ticket ID.

Ticket Type (ticket_type, default: fields/issuetype/name): Specify the path to the field containing the type for the ticket.

Ticket UID (artefact_uid, default: JR#${id}): Specify the pattern used to build the ticket Unique ID. The UID can use any information collected from the JSON file as a parameter.

Ticket Keys (artefact_keys, default: key): Specify the pattern used to find the ticket keys. The keys can use any information collected from the file, separated by ";".

Ticket Links (artefact_link, default: type/inward?array=fields/issuelinks,/inwardIssue/key&direction=IN;): Specify the pattern used to find the ticket links. The links can have special syntax, see import_generic_data documentation.

Creation Date Field (creation_date, default: fields/created): Enter the path to the field containing the creation date of the ticket.

Closure Date Field (closure_date, default: fields/resolutiondate): Enter the path to the field containing the closure date of the ticket.

Due Date Field (due_date, default: fields/duedate): Enter the path to the field containing the due date of the ticket.

Last Updated Date Field (last_updated_date, default: fields/updated): Enter the path to the field containing the last updated date of the ticket.

Time Spent (time_spent, default: fields/timespent): Specify the path to the field containing time spent on the issue.

Remaining Time (remaining_time, default: fields/timeestimate): Specify the path to the field containing the remaining time for the issue.

Original Time Estimate (original_time_estimate, default: fields/timeoriginalestimate): Specify the path to the field containing the original time estimate for the issue.

Open Ticket Pattern (definition_open, default: fields/status/name=[To Do|Open|Reopened]): Specify the pattern applied to define tickets as open. This field accepts a regular expression to match one or more column headers or path with a list of possible values.

In Development Ticket Pattern (definition_rd_progress, default: fields/status/name=[In Progress|In Review]): Specify the pattern applied to define tickets as in development. This field accepts a regular expression to match one or more path with a list of possible values.

Fixed Ticket Pattern (definition_vv_progress, default: fields/status/name=[Verified]): Specify the pattern applied to define tickets as fixed. This field accepts a regular expression to match one or more path with a list of possible values.

Closed Ticket Pattern (definition_close, default: fields/status/name=[Resolved|Closed|Done]): Specify the pattern applied to define tickets as closed. This field accepts a regular expression to match one or more path with a list of possible values.

Defect Pattern (definition_defect, default: fields/issuetype/name=[Bug]): Specify the pattern applied to define tickets as defects. This field accepts a regular expression to match one or more path with a list of possible values.

Enhancement Pattern (definition_enhancement, default: fields/issuetype/name=[Improvement|New Feature]): Specify the pattern applied to define tickets as enhancements. This field accepts a regular expression to match one or more path with a list of possible values.

Other Pattern (definition_other): Specify the pattern applied to define tickets of 'Other' types. This means not a defect or an enhancement. This field accepts a regular expression to match one or more column headers with a list of possible values.

Category (category, default: fields/components[0]/name): Specify the path to the field containing the ticket category.

Priority (priority, default: fields/priority/name): Specify the path to the field containing the ticket priority.

Severity (severity, default: fields/priority/name): Specify the path to the field containing severity data.

Severity Mapping (severity_mapping, default: [Lowest:0,Low:1,Medium:2,High:3,Highest:4]): Specify the mapping used to associate a severity to a scale on the severity scale in the model, where 0 is least critical and 4 is most critical.

Status (status, default: fields/status/name): Specify the path to the field containing the status of the ticket.

Information Fields (informations, default: fields/environment;fields/votes/votes): Specify a semicolon-separated list of paths to fields you want to extract from the Jira JSON export to be added as textual information for the ticket artefacts.

Issue URL (issue_url, default: ${self}/../../../../../browse/${key}): Specify the pattern used to build the ticket URL. The URL can use any information collected from the file as a parameter.

Title (title, default: fields/summary): Specify the path to the field containing the title of the ticket.

Description (description, default: fields/description): Specify the path to the field containing the full description of the ticket.

Reporter (reporter, default: fields/reporter/displayName): Specify the path to the field containing the reporter of the ticket.

Handler (handler, default: fields/assignee/displayName): Specify the path to the field containing the handler of the ticket.

Extract other artefacts (extract_artifacts): Extract other artefacts to be linked with the main artefact. Use the following format:

Additional Metrics Fields (custom_metrics): Specify a semicolon-separated list of paths to fields you want to extract from the Jira JSON export and to be added as extra metrics for the ticket artefacts.

Additional Date Fields (custom_metrics_date): Specify a semicolon-separated list of paths to fields you want to extract from the Jira JSON export and to be added as extra date information.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

JSHint results file (Checkstyle formatted): (xml, mandatory): Point to the XML file that contains JSHint results Checkstyle formatted.

Results folder (resultDir, mandatory): Specify the path to the folder containing the JUnit results (or by a tool able to produce data in this format). The data provider will parse subfolders recursively. Note that the minimum support version of JUnit is 4.10.

File Pattern (filePattern, mandatory, default: TEST-.xml)*: Specify the pattern for files to read reports from.

Root Artefact (root, mandatory, default: tests[type=TEST_FOLDER]/junit[type=TEST_FOLDER]): Specify the name and type of the artefact under which the test artefacts will be created.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

XML results file (xml, mandatory): Specify the path to the XML results file exported from Klocwork. Note that Klocwork version 9.6.1 is the minimum required version.

Use specific ruleset (ruleset, default: klocwork): Specify which ruleset to use.

defaultToFile(default: true): Set the following field to false to not attach the results to the file, if the function is not found. By default, it's true.

generateRelaxedFindings(default: false): set the following field to true to produce findings for ignored states or statuses. By default, it's false

stateToIgnore(default: Fixed): List of state for which a finding does not need to be created, separated by comma.

statusToIgnore(default: Ignore,Defer,Not a Problem): List of citingStatus for which a finding does not need to be created, separated by comma.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

XML results file (xml, mandatory): Specify the path to the XML results file exported from Klocwork. Note that Klocwork version 9.6.1 is the minimum required version.

defaultToFile(default: true): Set the following field to false to not attach the results to the file, if the function is not found. By default, it's true.

generateRelaxedFindings(default: false): set the following field to true to produce findings for ignored states or statuses. By default, it's false

stateToIgnore(default: Fixed): List of state for which a finding does not need to be created, separated by comma.

statusToIgnore(default: Ignore,Defer,Not a Problem): List of citingStatus for which a finding does not need to be created, separated by comma.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Choose Excel or CSV import (import_type, default: excel): Specify if the import is about Excel or CSV.

File or Directory (xls_file, mandatory): Specify the location of the Excel or CSV file or directory containing Memory information.

Sheet Name (xls_sheetname, mandatory): Specify the name of the Excel sheet that contains the Memory list.

Excel file regular expression (xlsx_file_pattern, default: *.xlsx$): Specify a regular expression to find Excel files, by default it's *.xlsx$

Specify the CSV separator (csv_separator, default: ;): Specify the CSV separator

CSV file regular expression (csv_file_pattern, default: *.csv$): Specify a regular expression to find CSV files, by default it's *.csv$

Memory Column name (xls_key, mandatory): Specify the header name of the column which contains the Memory key.

Memory artefact root path (root_node, default: Resources): Specify the root path in Squore of artefacts extracted from the file.

Grouping Structure (xls_groups): Artifacts can be grouped by contextual elements of the file, separated by ";".

Filtering (xls_filters): Specify the list of Header for filtering

Memory size column name (memory_size_column_name, default: Total): Specify the header name of the column which contains the memory size.

Used memory column name (memory_used_column_name, default: Used): Specify the header name of the column which contains the used memory.

Memory type column name (memory_type_column_name, default: Type): Specify the header name of the column which contains the memory type.

ROM memory type name (memory_type_rom_name, default: ROM): Specify the name used for ROM memory.

RAM memory type name (memory_type_ram_name, default: RAM): Specify the name used for RAM memory.

NVM memory type name (memory_type_nvm_name, default: NVM): Specify the name used for NVM memory.

Create an output file (createOutput, default: true): Create an output file

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Code Folder (logDir): Specify the path to the folder that contains the annotated files to process.

Extension (ext, default: html): Specify the extension used by QAC to create annotated files.

Force import of all QAC violations (not only MISRA) (force_all_import, default: false): Force the import of all QAC findings ( not only the MISRA violations)

Results File Format (file_format, mandatory): PC-lint Plus output file can be generated using the following lnt configuration:

Xml Results File (results): Specify the path to the PC-lint Plus xml results file.

Text Results File (text_file): Specify the path to the PC-lint Plus text results file.

Synchronize PC-lint Plus Configuration (update_rules, default: false): Providing the lnt files allows synchronizing the Squore ruleset with regard to what was really activated during PC-lint Plus analysis.

Configuration Files (.lnt) (config_files, mandatory)*: Path to PC-lint Plus lnt configuration files.

Standards (convert_standard, mandatory): Choose the standards to activate among the available Standards defined in the lnt configuration files.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE). The default is INFO

XML results file or directory (xml, mandatory): Specify the path to the PMD XML or JSON results file(s) or directory. Note that the minimum supported version of PMD for this data provider is 4.2.5.

Regex Files (regexFile, mandatory, default: .xml): Specify a regular expression to find PMD XML files

PMD SARIF format results (isSarifFormat): Check the box if the PMD result files are in SARIF format. Leave it unchecked to work with XML files instead.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE)

Source code folder (customDirs): Specify the folder containing the source files to analyse. If you want to analyse all of source repositories specified for the project, select None.

Ruleset file (configFile): Specify the path to the PMD XML ruleset you want to use for this analysis. If you do not specify a ruleset, the default one from INSTALLDIR/addons/tools/PMD_auto will be used.

Memory Allocation (xmx, default: 1024m): Maximum amount of memory allocated to the java process launching PMD.

PMD SARIF format results (outputSarifFormat): Output results in SARIF instead of XML

Results file (csv, mandatory): Specify the path to the CSV report file created by pep8. The output format will be the default or pylint format.

CSV results file (csv, mandatory): Specify the path to the CSV file containing pylint results. Note that the minimum version supported is 1.1.0.

Source code directory to analyse (dir): Leave this field empty to analyse all sources.

QAC output file(s) (txt, mandatory): Specify the path(s) to the .tab file(s) to extract findings from. To provide multiple files click on '+'

Eliminate duplicated findings (eliminateDuplicate, default: false): When 2 occurences of the same finding (same rule, same file, same line, same description) is found, only one is reported.

C Coding Standards (cCodingStandard, default: misra): Speficy the C Coding Standards used

fileName(default: Filename with path): Speficy the file name header in the file, by default it is "Filename with path".

line(default: Line): Speficy the line number header in the file, by default it is "Line".

description(default: Message text): Speficy the description header in the file, by default it is "Message text".

rule(default: Rule): Speficy the rule header in the file, by default it is "Rule".

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

regexFile(default: .tab$): Specify a regular expression to find QAC tab files

fileSeparator(default: \t): Specify the File separator, required on File import

default2application(default: true): If this field is "true": when a file is not found for a rule, a finding is added to the Artefact application. By default it is true.

QAC CERT output file(s) (txt, mandatory): Specify the path(s) to the .tab file(s) to extract findings from. To provide multiple files click on '+'

Eliminate duplicated findings (eliminateDuplicate, default: false): When 2 occurences of the same finding (same rule, same file, same line, same description) is found, only one is reported.

fileName(default: Filename with path): Speficy the file name header in the file, by default it is "Filename with path".

line(default: Line): Speficy the line number header in the file, by default it is "Line".

description(default: Message text): Speficy the description header in the file, by default it is "Message text".

rule(default: Rule): Speficy the rule header in the file, by default it is "Rule".

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

regexFile(default: .tab$): Specify a regular expression to find QAC tab files

fileSeparator(default: \t): Specify the File separator, required on File import

default2application(default: true): If this field is "true": when a file is not found for a rule, a finding is added to the Artefact application. By default it is true.

QAC CWE output file(s) (txt, mandatory): Specify the path(s) to the .tab file(s) to extract findings from. To provide multiple files click on '+'

Eliminate duplicated findings (eliminateDuplicate, default: false): When 2 occurences of the same finding (same rule, same file, same line, same description) is found, only one is reported.

fileName(default: Filename with path): Speficy the file name header in the file, by default it is "Filename with path".

line(default: Line): Speficy the line number header in the file, by default it is "Line".

description(default: Message text): Speficy the description header in the file, by default it is "Message text".

rule(default: Rule): Speficy the rule header in the file, by default it is "Rule".

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

regexFile(default: .tab$): Specify a regular expression to find QAC tab files

fileSeparator(default: \t): Specify the File separator, required on File import

default2application(default: true): If this field is "true": when a file is not found for a rule, a finding is added to the Artefact application. By default it is true.

QAC HIS output file(s) (txt, mandatory): Specify the path(s) to the .tab file(s) to extract findings from. To provide multiple files click on '+'

Eliminate duplicated findings (eliminateDuplicate, default: false): When 2 occurences of the same finding (same rule, same file, same line, same description) is found, only one is reported.

fileName(default: Filename with path): Speficy the file name header in the file, by default it is "Filename with path".

line(default: Line): Speficy the line number header in the file, by default it is "Line".

description(default: Message text): Speficy the description header in the file, by default it is "Message text".

rule(default: Rule): Speficy the rule header in the file, by default it is "Rule".

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

regexFile(default: .tab$): Specify a regular expression to find QAC tab files

fileSeparator(default: \t): Specify the File separator, required on File import

default2application(default: true): If this field is "true": when a file is not found for a rule, a finding is added to the Artefact application. By default it is true.

QAC MISRA output file(s) (txt, mandatory): Specify the path(s) to the .tab file(s) to extract findings from. To provide multiple files click on '+'

Eliminate duplicated findings (eliminateDuplicate, default: false): When 2 occurences of the same finding (same rule, same file, same line, same description) is found, only one is reported.

fileName(default: Filename with path): Speficy the file name header in the file, by default it is "Filename with path".

line(default: Line): Speficy the line number header in the file, by default it is "Line".

description(default: Message text): Speficy the description header in the file, by default it is "Message text".

rule(default: Rule): Speficy the rule header in the file, by default it is "Rule".

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

regexFile(default: .tab$): Specify a regular expression to find QAC tab files

fileSeparator(default: \t): Specify the File separator, required on File import

default2application(default: true): If this field is "true": when a file is not found for a rule, a finding is added to the Artefact application. By default it is true.

RuleChecker results file (csv, mandatory): Specify the path to the CSV results file from Logiscope.

Input file (input_file, mandatory): Specify the location of the Excel file or directory containing information.

Sheetname (sheetname, mandatory): Sheetname to read data from

Artefact name (artefact_name, mandatory): Artefact name as displayed in Squore. Examples:

Path to the artefact (path_list): Optional. If not used, artefacts extracted from the Excel file will be directly added to the Squore root.

Textual data to extract (info_list): Optional.

Numerical metrics to extract (metric_list): Optional.

Artefact unique ID (artefact_uid): Optional unless you want to use links to these artefacts.

Excel file regular expression (xlsx_file_pattern, default: *.xlsx$): Specify a regular expression to find Excel files, by default it's *.xlsx$

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Choose Excel, CSV, JSON or XML import (import_type, default: excel): Specify if the import is about Excel, CSV, JSON or Xml file.

Data File (input_file, mandatory): Specify the location of the file or directory containing Excel, CSV, JSON or XML files with requirements.

Sheet Name (xls_sheetname): Specify the sheet name that contains the requirement list.

Excel file regular expression (xlsx_file_pattern, default: *.xlsx$): Specify a regular expression to find Excel files, by default it's *.xlsx$

CSV Separator (csv_separator, default: ;): Specify the character used in the CSV file to separate columns.

CSV file regular expression (csv_file_pattern, default: *.csv$): Specify a regular expression to find CSV files, by default it's *.csv$

List of future artifacts (root_path): Defined the root element to retrieve the list of artifacts in the file, required on JSON or XML import.

JSON file regular expression (json_file_pattern, default: *.json$): Specify a regular expression to find JSON files, by default it's *.json$

XML file regular expression (xml_file_pattern, default: *.xml$): Specify a regular expression to find XML files, by default it's *.xml$

Requirement Name (artefact_name, mandatory): Required Specify the pattern used to build the name of the requirement. The name can use any information collected from the file as a parameter.

Requirement artefact path (root_node, default: Requirements): Specify the root path in Squore of artefacts extracted from the file.

Requirement ID (artefact_id, mandatory): Specify the column name or path which contain the requirement ID.

Requirement version (version): Specify the column name or path which contain the requirement version.

Linked Requirements IDs which satisfy this requirement (link_satisfied_by): Specify the column name or path which contain the requirements IDs which satisfy this requirement.

Linked Test ID verifying this requirement (link_tested_by): Specify the column name or path which contain the linked test ID verifying this requirement.

Linked Ticket ID associated to this requirement (link_ticket): Specify the column name or path which contain the linked Ticket ID corresponding to an issue or enhancement request.

Requirement UID (artefact_uid): Specify the pattern used to build the requirement Unique ID. The UID can use any information collected from the file as a parameter.

Grouping Structure (artefact_groups): Artifacts can be grouped by contextual elements of the file, separated by ";".

Filtering (artefact_filters): If specified: only artefacts complying with the provided filters are kept. Use the following format:

Status (status, default: Status): Specify the status of requirement.

Applicable Requirement Pattern (definition_applicable): Specify the pattern applied to define requirements as Applicable. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Proposed Requirement Pattern (definition_proposed): Specify the pattern applied to define requirements as proposed. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Analyzed Requirement Pattern (definition_analyzed): Specify the pattern applied to define requirements as analyzed. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Approved Requirement Pattern (definition_approved): Specify the pattern applied to define requirements as approved. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Implemented Pattern (definition_implemented): Specify the pattern applied to define requirements as Implemented. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Verified Requirement Pattern (definition_verified): Specify the pattern applied to define requirements as Verified. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Postponed Requirement Pattern (definition_postponed): Specify the pattern applied to define requirements as Postponed. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Deleted Requirement Pattern (definition_deleted): Specify the pattern applied to define requirements as deleted. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Rejected Requirement Pattern (definition_rejected): Specify the pattern applied to define requirements as rejected. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Priority Column (priority): Specify the header of the column containing priority data.

'Very high' Requirement priority Pattern (definition_priority_very_high): Specify the pattern applied to define requirements priority as 'Very High' (usually associated to value '1'). This field accepts a regular expression to match one or more column name or path with a list of possible values.

'High' Requirement priority Pattern (definition_priority_high): Specify the pattern applied to define requirements priority as 'High' (usually associated to value '2'). This field accepts a regular expression to match one or more column name or path with a list of possible values.

'Medium' Requirement priority Pattern (definition_priority_medium): Specify the pattern applied to define requirements priority as 'Medium' (usually associated to value '3'). This field accepts a regular expression to match one or more column name or path with a list of possible values.

'Low' Requirement priority Pattern (definition_priority_low): Specify the pattern applied to define requirements priority as 'Low' (usually associated to value '4'). This field accepts a regular expression to match one or more column name or path with a list of possible values.

Compliance (compliance, default: Compliance): Specify the compliance of requirement.

'Met' Compliance Pattern (definition_met): Specify the pattern applied to define requirement Compliance as 'Met'. This field accepts a regular expression to match one or more column name or path with a list of possible values.

'Partially Met' Compliance Pattern (definition_partially_met): Specify the pattern applied to define requirement Compliance as 'Partially Met'. This field accepts a regular expression to match one or more column name or path with a list of possible values.

'Not Met' Compliance Pattern (definition_not_met): Specify the pattern applied to define requirement Compliance as 'Not Met'. This field accepts a regular expression to match one or more column name or path with a list of possible values.

IADT (iadt, default: IADT Method): Specify the IADT of requirement.

'Inspection' Test Method Pattern (definition_inspection): Specify the pattern applied to define requirement Test method as 'Inspection'. This field accepts a regular expression to match one or more column name or path with a list of possible values.

'Analysis' Test Method Pattern (definition_analysis): Specify the pattern applied to define requirement Test method as 'Analysis'. This field accepts a regular expression to match one or more column name or path with a list of possible values.

'Demonstration' Test Method Pattern (definition_demonstration): Specify the pattern applied to define requirement Test method as 'Demonstration'. This field accepts a regular expression to match one or more column name or path with a list of possible values.

'Test' Test Method Pattern (definition_test): Specify the pattern applied to define requirement Test method as 'Test'. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Creation Date (creation_date): Specify the column name or path which contain the creation date of the requirement.

Last Update (last_updated): Specify the column name or path which contain the last modification date of the requirement.

URL (url): Specify the pattern used to build the requirement URL. The URL can use any information collected from the CSV file as a parameter.

Description Column (description): Specify the header of the column containing the description of the requirement.

Criticity (criticity, default: Criticity): Specify the criticity of requirement.

'A' critical factor Pattern (definition_crit_factor_A): Specify the pattern applied to define requirement critical factor as 'A' (low). This field accepts a regular expression to match one or more column name or path with a list of possible values.

'B' critical factor Pattern (definition_crit_factor_B): Specify the pattern applied to define requirement critical factor as 'B' (medium). This field accepts a regular expression to match one or more column name or path with a list of possible values.

'C' critical factor Pattern (definition_crit_factor_C): Specify the pattern applied to define requirement critical factor as 'C' (high). This field accepts a regular expression to match one or more column name or path with a list of possible values.

'D' critical factor Pattern (definition_crit_factor_D): Specify the pattern applied to define requirement critical factor as 'D' (highest). This field accepts a regular expression to match one or more column name or path with a list of possible values.

Information Fields (informations): Specify the list of extra textual information to import from the file. This parameter expects a list of column name or path separated by ";" characters.

Date format (date_format, default: yyyy-MM-dd): Formatting the date to match the given pattern. This pattern can be used for "Last Update" and "Creation Date" fields and "&format" parameter is no longer requiredFor examples: "dd/mm/yyyy" or "yyyy-MM-dd'T'hh:mm:ss'Z'" Note:Date patterns are based on SimpleDateFormat Java class specifications.

Save Output (createOutput):

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

JSon File(s) (sarifFile, mandatory): Specify the JSon file (or the directory) which contains the findings results

Finding description pattern (findingPattern): The list of patterns to apply to finding description.

Rules exclusion pattern (excludedRules): Specify rules to be excluded by a pattern. The syntax will be ruleField=pattern.

Search by file name only (ignoreArtPath): Checking the box allows to search matching file only by file name instead of using the entire path

tool(default: true): Checking the box save the tool name in input-data.xml.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Languages (languages, default: ada;c;cpp;csharp;cobol;java;fortran77;fortran90;groovy;php;python;swift;vbn…​): Check the boxes for the languages used in the specified source repositories. Adjust the list of file extensions as necessary. Note that two languages cannot use the same file extension, and that the list of extensions is case-sensitive. Tip: Leave all the boxes unchecked and Squore Analyzer will auto-detect the language parser to use.

Force full analysis (rebuild_all, default: false): Analyses are incremental by default. Check this box if you want to force the source code parser to analyse all files instead of only the ones that have changed since the previous analysis. This is useful if you added new rule files or text parsing rules and you want to re-evaluate all files based on your modifications.

Generate control graphs (genCG, default: true): this option is deprecated and will be removed in a future release. You should not use it anymore.

Use qualified names (qualified, default: false): Note: This option cannot be modified in subsequent runs after you create the first version of your project.

Limit analysis depth (depth, default: false): this option is deprecated and will be removed in a future release. You should not use it anymore.

Add a 'Source Code' node (scnode, default: false): Using this options groups all source nodes under a common source code node instead of directly under the APPLICATION node. This is useful if other data providers group non-code artefacts like tests or requirements together under their own top-level node. This option can only be set when you create a new project and cannot be modified when creating a new version of your project.

'Source Code' node label (scnode_name, default: Source Code): Specify a custom label for your main source code node. Note: this option is not modifiable. It only applies to projects where you use the "Add a 'Source Code' node" option. When left blank, it defaults to "Source Code".

Compact folders (compact_folder, default: true): this option is deprecated and will be removed in a future release. You should not use it anymore.

Content exclusion via regexp (pattern): Specify a PERL regular expression to automatically exclude files from the analysis if their contents match the regular expression. Leave this field empty to disable content-based file exclusion.

File Filtering (files_choice, default: Exclude): Specify a pattern and an action to take for matching file names. Leave the pattern empty to disable file filtering.

pattern (pattern_files): Use a shell-like wildcard e.g. '*-test.c'.

Folder Filtering (dir_choice, default: Exclude): Specify a pattern and an action to take for matching folder names. Leave the pattern empty to disable folder filtering.

pattern (pattern_dir): Use a shell-like wildcard e.g. 'Test_*'.

Exclude files whose size exceeds (size_limit, default: 500000): Provide the size in bytes above which files are excluded automatically from the Squore project (Big files are usually generated files or test files). Leave this field empty to deactivate this option.

Detect algorithmic cloning (clAlg, default: true): When checking this box, Squore Analyzer launches a cloning detection tool capable of finding algorithmic cloning in your code.

Detect text cloning (clTxt, default: true): When checking this box, Squore Analyzer launches a cloning detection tool capable of finding text duplication in your code.

Ignore blank lines (clIgnBlk, default: true): When checking this box, blanks lines are ignored when searching for text duplication

Ignore comment blocks (clIgnCmt, default: true): When checking this box, blocks of comments are ignored when searching for text duplication

Minimum size of duplicated blocks (clRSlen, default: 10): This threshold defines the minimum size (number of lines) of blocks that can be reported as cloned.

Textual Cloning fault ratio (clFR, default: 0.1): This threshold defines how much cloning between two artefacts is necessary for them to be considered as clones by the text duplication tool. For example, a fault ratio of 0.1 means that two artefacts are considered clones if less than 10% of their contents differ.

Algorithmic cloning fault ratio (clAlgFR, default: 0.1): This threshold defines how much cloning between two artefacts is necessary for them to be considered as clones by the algorithmic cloning detection tool.

Compute Textual stability (genTs, default: true): this option is deprecated and will be removed in a future release. You should not use it anymore.

Compute Algorithmic stability (genAs, default: true): this option is deprecated and will be removed in a future release. You should not use it anymore.

Detect artefact renaming (clRen, default: true): this option is deprecated and will be removed in a future release. You should not use it anymore.

Mark relaxed or confirmed findings as suspicious (susp, default: MODIFIED_BEFORE): Depending on the choosen option, relaxed findings can be flagged as suspicious in case of changes in and around the finding. In all cases, the following is to be considered:

Accept Relaxation from source code comment (relax, default: true): Relaxing Violations in Code

Function calls as links (C language only) (calls, default: false): When selecting this option a link between caller and called will be imported (link of type CALLS).

Additional parameters (additional_param): These additional parameters can be used to pass instructions to external processes started by this data provider. This value is generally left empty in most cases.

XML folder (inputDir, mandatory): Specify the folder that contains the squore_data_*.xml files that you want to import.

Choose Excel or CSV import (import_type, default: excel): Specify if the import is about Excel or CSV.

File or Directory (xls_file, mandatory): Specify the location of the Excel or CSV file or directory containing Stack information.

Sheet Name (xls_sheetname): Specify the sheetname that contains the Stack list.

Excel file regular expression (xlsx_file_pattern, default: *.xlsx$): Specify a regular expression to find Excel files, by default it's *.xlsx$

Specify the CSV separator (csv_separator, default: ;): Specify the CSV separator

CSV file regular expression (csv_file_pattern, default: *.csv$): Specify a regular expression to find CSV files, by default it's *.csv$

Stack Column name (xls_key, mandatory): Specify the header name of the column which contains the Stack key.

Stack artefact root path (root_node, default: Resources): Specify the root path in Squore of artefacts extracted from the file.

Grouping Structure (xls_groups): Artifacts can be grouped by contextual elements of the file, separated by ";".

Filtering (xls_filters): Specify the list of Header for filtering

Stack size column (stack_size_column_name, default: Stack Size [Bytes]): Specify the name of the column of Stack Size

Stack Average column (stack_average_column_name, default: Average Stack Size used [Bytes]): Specify the name of the column of Stack Average

Stack Worst column (stack_worst_column_name, default: Worse Case Stack Size used [Bytes]): Specify the name of the column of Stack Worst

Create an output file (createOutput, default: true): Create an output file

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

XML results file (xml, mandatory): Specify the path to the StyleCop XML results file. The minimum version compatible with this data provider is 4.7.

Results folder (resultDir, mandatory): Specify the top folder containing XML result files from Tessy. Note that this data provider will recursively scan sub-folders looking for *.xml files to aggregate results.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE)

Choose Excel, CSV, JSON or XML import (import_type, default: excel): Specify if the import is about Excel, CSV, JSON or Xml file.

Data File (input_file, mandatory): Specify the location of the Excel, CSV, JSON or XML file or directory containing tests.

Excel Sheet Name (xls_sheetname): Specify the sheet name that contains the test list if your import file is in Excel format.

Excel file regular expression (xlsx_file_pattern, default: *.xlsx$): Specify a regular expression to find Excel files, by default it's *.xlsx$

CSV Separator (csv_separator, default: ;): Specify the character used in the CSV file to separate columns.

CSV file regular expression (csv_file_pattern, default: *.csv$): Specify a regular expression to find CSV files, by default it's *.csv$

JSON file regular expression (json_file_pattern, default: *.json$): Specify a regular expression to find JSON files, by default it's *.json$

XML file regular expression (xml_file_pattern, default: *.xml$): Specify a regular expression to find XML files, by default it's *.xml$

Test Name (artefact_name, mandatory): Specify the pattern used to build the name of the test. The name can use any information collected from the file as a parameter.

List of future artifacts (root_path): Defined the root element to retrieve the list of artifacts in the file, required on JSON or XML import.

Test artefact path (root_node, default: Tests): Specify the root path in Squore of artefacts extracted from the file.

TestID (artefact_id): Specify the column name or path which contain the test ID.

Linear Index (linear_idx): Specify the column name or path of the Linear Index (=Linear Index is used to order unit or integration tests in matrix graph).

Test UID (artefact_uid): Specify the pattern used to build the test Unique ID. The UID can use any information collected from the file as a parameter.

Grouping Structure (artefact_groups): Artifacts can be grouped by contextual elements of the file, separated by ";".

Filtering (artefact_filters): If specified: only artefacts complying with the provided filters are kept. Use the following format:

Failed Test Pattern (definition_failed): Specify the pattern applied to define tests as failed. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Inconclusive Test Pattern (definition_inconclusive): Specify the pattern applied to define tests as inconclusive. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Passed Test Pattern (definition_passed): Specify the pattern applied to define tests as passed. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Status (status, default: status): Specify the status test.

Date when the test was executed (execution_date): Enter column name or path containing the execution date of the test.

Unit of test duration (execution_duration_unit, default: 1): Enter the unit used for the test duration. Possible values are 's' (seconds) or 'ms' (milliseconds), default is 'ms')

Duration of the test (execution_duration): Enter column name or path containing the execution duration of the test, in milliseconds.

TODO Pattern (in_todo_list): Specify the pattern applied to include tests in the TODO list. This field accepts a regular expression to match one or more column name or path with a list of possible values.

Creation Date (creation_date): Enter column name or path containing the creation date of the test.

Last Updated Date (last_updated_date): Enter column name or path containing the last updated date of the test.

URL (url): Specify the pattern used to build the test URL. The URL can use any information collected from the file as a parameter.

Description (description): Specify column name or path containing the description of the test.

Category (category): Specify column name or path containing the category of the test.

Priority (priority): Specify column name or path containing priority data.

Information Fields (informations): Specify the list of extra textual information to import from the file. This parameter expects a list of headers separated by ";" characters.

Date format (date_format, default: yyyy-MM-dd): Formatting the date to match the given pattern. This pattern can be used for "Last Updated Date", "Creation Date" and "Date when the test was executed" fields and "&format" parameter is no longer requiredFor examples: "dd/mm/yyyy" or "yyyy-MM-dd'T'hh:mm:ss'Z'" Note:Date patterns are based on SimpleDateFormat Java class specifications.

Save Output (createOutput):

config_file: Specify the path to configuration file containing Test import parameters.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Input file (input_file): Specify the location of the Excel file or directory containing test information.

Sheetname (sheetname, mandatory): Sheetname to read data from

Artefact name (artefact_name, mandatory): Artefact name as displayed in Squore. Examples:

Path to the artefact (path_list): Optional. If not used, artefacts extracted from the Excel file will be directly added to the Squore root.

Textual data to extract (info_list): Optional.

Numerical metrics to extract (metric_list): Optional.

Date metrics to extract (date_list): Optional.

Filters to set the list of artefacts to keep (filter_list): Optional.

Artefact unique ID (artefact_uid): Optional unless you want to use links to these artefacts.

Links to this artefact (artefact_link): Specify how to create links between this artefact and other artefacts with the following format:

Excel file regular expression (xlsx_file_pattern, default: *.xlsx$): Specify a regular expression to find Excel files, by default it's *.xlsx$

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Results folder (dir, mandatory): Specify the folder containing XML test results files from Testwell CTC++.

Instrumented files extension (extension, mandatory, default: .test.runner.c): Instrumented files extension (Extension of the instrumented files generated by ctc++)

Choose Excel, CSV, JSON or XML import (import_type, default: excel): Specify if the import is about Excel, CSV, JSON or Xml file.

Data File (input_file, mandatory): Specify the location of the Excel, CSV, JSON or XML file or directory containing tickets.

Excel Sheet Name (xls_sheetname): Specify the sheet name that contains the ticket list if your import file is in Excel format.

Excel file regular expression (xlsx_file_pattern, default: *.xlsx$): Specify a regular expression to find Excel files, by default it's *.xlsx$

CSV Separator (csv_separator, default: ;): Specify the character used in the file to separate columns. Have to be specified if the imported file is CSV type

CSV file regular expression (csv_file_pattern, default: *.csv$): Specify a regular expression to find CSV files, by default it's *.csv$

JSON/XML Root Path (root_path): Specify the root path in the JSON or XML file to retrieve issues. Have to be specified if the imported file is JSON type or XML type.

JSON file regular expression (json_file_pattern, default: *.json$): Specify a regular expression to find JSON files, by default it's *.json$

XML file regular expression (xml_file_pattern, default: *.xml$): Specify a regular expression to find XML files, by default it's *.xml$

Ticket Name (artefact_name, mandatory): Specify the pattern used to build the name of the ticket. The name can use any information collected from the file as a parameter.

Root Node (root_node, default: Tickets): Specify the name of the node to attach tickets to.

Ticket ID (artefact_id, mandatory): Specify the header name or of the column or path which contains the ticket ID.

Ticket Type (ticket_type): Specify the header of the column or path containing the type for the issue.

Ticket Keys (artefact_keys): Specify the list of keys to import from the file. This parameter expects a list of headers or path separated by ";" characters.

Ticket Links (artefact_link): Specify the pattern used to find the ticket links. The links can have special syntax, see import_generic_data documentation.

Ticket UID (artefact_uid): Specify the pattern used to build the ticket Unique ID. The UID can use any information collected from the file as a parameter.

Grouping Structure (artefact_groups): Specify the headers for Grouping Structure, separated by ";".

Filtering (artefact_filters): Specify the list of Header or path for filtering

Open Ticket Pattern (definition_open): Specify the pattern applied to define tickets as open. This field accepts a regular expression to match one or more column headers or path with a list of possible values.

In Development Ticket Pattern (definition_rd_progress): Specify the pattern applied to define tickets as in development. This field accepts a regular expression to match one or more column headers or path with a list of possible values.

Fixed Ticket Pattern (definition_vv_progress): Specify the pattern applied to define tickets as fixed. This field accepts a regular expression to match one or more column headers or path with a list of possible values.

Closed Ticket Pattern (definition_close): Specify the pattern applied to define tickets as closed. This field accepts a regular expression to match one or more column headers or path with a list of possible values.

Defect Pattern (definition_defect): Specify the pattern applied to define tickets as defects. This field accepts a regular expression to match one or more column headers or path with a list of possible values.

Enhancement Pattern (definition_enhancement): Specify the pattern applied to define tickets as enhancements. This field accepts a regular expression to match one or more column headers or path with a list of possible values.

Other Pattern (definition_other): Specify the pattern applied to define tickets of 'Other' types. This means not a defect or an enhancement. This field accepts a regular expression to match one or more column headers with a list of possible values.

TODO Pattern (in_todo_list): Specify the pattern applied to include tickets in the TODO list. This field accepts a regular expression to match one or more column headers or path with a list of possible values.

Creation Date Column or Path (creation_date): Enter the name of the column or path containing the creation date of the ticket. If the pattern to format date isn't the same as the "Date format" field, the parameter format="date_pattern" can be used.

Due Date Column or Path (due_date): Enter the name of the column or path containing the due date of the ticket. If the pattern to format date isn't the same as the "Date format" field, the parameter format="date_pattern" can be used.

Last Updated Date Column or Path (last_updated_date): Enter the name of the column or path containing the last updated date of the ticket. If the pattern to format date isn't the same as the "Date format" field, the parameter format="date_pattern" can be used.

Closure Date Column or Path (closure_date): Enter the name of the column or path containing the closure date of the ticket. If the pattern to format date isn't the same as the "Date format" field, the parameter format="date_pattern" can be used.

Time Spent (time_spent): Specify the header of the column or path containing time spent on the issue.

Remaining Time (remaining_time): Specify the header of the column or path containing the remaining time for the issue.

Original Time Estimate (original_time_estimate): Specify the header of the column or path containing the original time estimate for the issue.

Status Column or Path (status, default: Status): Specify the header of the column or path containing the status of the ticket.

URL (url): Specify the pattern used to build the ticket URL. The URL can use any information collected from the file as a parameter.

Title Column or Path (title): Specify the header of the column or path containing the title of the ticket.

Description Column or Path (description): Specify the header of the column or path containing the description of the ticket.

Category Column or Path (category): Specify the header of the column or path containing the category of the ticket.

Reporter Column or Path (reporter): Specify the header of the column or path containing the reporter of the ticket.

Handler Column or Path (handler): Specify the header of the column or path containing the handler of the ticket.

Priority Column or Path (priority): Specify the header of the column or path containing priority data.

Severity Column or Path (severity): Specify the header of the column or path containing severity data.

Severity Mapping (severity_mapping): Specify the mapping used to associate a severity to a scale on the severity scale in the model, where 0 is least critical and 4 is most critical.

Ticket Type (type, default: Type): The Ticket type for example defect or enhancement

Date format (date_format, default: yyyy-MM-dd): Formatting the date to match the given pattern. This pattern will be applied to all date fields.

Information Fields (informations): Specify the list of extra textual information to import from the file. This parameter expects a list of headers or path separated by ";" characters.

Additional Metrics Fields (custom_metrics): Specify the list of extra metrics to import from the file. This parameter expects a list of headers or path separated by ";" characters.

Additional Date Fields (custom_metrics_date): Specify the list of extra date information to import from the file. This parameter expects a list of headers or path separated by ";" characters.

Extract other artifacts (extract_artifacts): Extract other artifacts to be linked with the main artifact. Use the following format:

Save Output (createOutput):

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Trace Items folder (dir, mandatory): Specify the folder containing Trace Items (Requirements) files

Trace Items file suffix (suff, mandatory, default: .vti-tso): Provide the suffix of Trace Items (Requirements) files.

Add "Unique Id" to name (addIdToName, default: false): Add Unique Id to name (the unique id will be added at the end of the artefact name).

Add Readable ID (addReadableId, default: false): Add Readable ID (the readable id will be added at the beginning of the artefact name)

Planned Trace Items folder (dirPlanned): Specify the folder containing Planned Trace Items files.

Filter on Requirements (filter): The filter is a way to keep Requirements which properties match a certain pattern.

Requirements grouping (grouping): Grouping is a way to structure Requirements in Squore by the value of given properties, in the order they are provided.

Textual information to extract (infoList, default: STATUS?property=Status&map=[In progress:under review];VERIFICATION_METHOD?p…​): To specify the list of textual data to extract from the vTraceitem properties.

Metric information to extract (metricList, default: REQ_STATUS?property=Status&map=[rejected:0,obsolete:0,draft:2,accept:1];RE…​)*: To specify the list of metric data to extract from the vTraceitem properties.

Reset Review flags (reset_review, default: false): Reset Review flags is used to initialize all review flags to "false".

Reset Overload flags (reset_overload, default: false): Reset Overload flags is used to initialize all overload flags to "default status".

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

Retrieve the coverage data via vectorCAST API? (generate_report, mandatory): Squore imports vectorCAST data via "report.xml" files.

VectorCAST project configuration files (Path to vcm, vce or vcp) (project_file_list): Specify the path to your project configuration file.

Folder of vectorCAST data files (ie, vectorcast_report.xml) (squore_report_folder): Specify the folder which contains all the vectorCAST data files (ie, vectorcast_report.xml).

Import variant data? (create_variant, default: false): Variant data can be imported beside the test results. It is possible to get an overview of the tests results per variant. CARREFUL: a variant key must be defined.

Variant key (variant_options, default: compiler;testsuite;group): Variant key allows to name the variant according relevant variant property. Key=compiler;testsuite will list all the variant and name them according the value of the field "Compiler/TestSuite".

Advanced options (advanced_options, default: false):

Root Artefact (sub_root, default: Tests): Specify the name of the artefact under which the test artefacts will be created.

Unit Tests folder (sub_root_for_unit, default: Unit Tests): Specify the name of the artefact under which the unit tests artefacts will be created.

System Tests folder (sub_root_for_system, default: System Tests): Specify the name of the artefact under which the system tests artefacts will be created.

Don’t Be "case sensitve" (case_sensitve_option, default: true): Don't Be "case sensitve"

Generate a testcase unique id (create_path_unique_id, default: false): Generate a testcase unique id based on "path + test name"

VectorCAST Dir (vectorcast_dir): In case you want to trigger a specific version of vectorCAST, you can specify the value of the %VECTORCAST_DIR%.

VectorCAST version (vectorcast_version, default: Version 20): This option is useful when vectorcast_dir option is set.

Ignore Missing Files (ignoreMissingFiles, default: true): This option must be used to ignore files which are found in vectorCAST database but not in the scope of the Squore Analysis.

logLevel(default: INFO): Specify the log level to be used (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF, TRACE) the default is INFO

You have only one node of source code in your project

You have more than one node of source code in your project