Overview
The sanity checker command line checks the test and fixture rules.
Sanity checker command
xtr
sanity_checker
# Path to folder where to find the testing project.
--source_path
# Options for the checks.
--checks
# Options for the meta data schema file name.
--schema
xtr The command to run XTR.
sanity_checker:
source_path: or sp: The path to the testing project to be checked.
checks: or c: Different checks can be done one by one or all toguether: imports,hardcoded_var,metadata,functions_rules,linter,init
schema: or s: The json file that contains different metedata fields to be respected.
Example of schema file
{
"type": "object",
"properties": {
"ASIL": {
"type": "array",
"items": {
"type": "string",
"enum": ["QM", "A", "B", "C", "D", "A(B)", "A(C)", "A(D)", "B(C)", "B(D)", "C(D)"]
}
},
"derivationTechnique": {
"type": "string",
"enum": [
"Analysis of requirements",
"Analysis of boundary values"
]
},
"domain": {
"type": "string",
"enum": [
"Interior Camera System",
"Debug log and trace",
"Mid Range Radar",
"Parking"
]
},
"verifies": {
"type": "array",
"items": {
"type": "string",
"enum": [
"ETH_SYS_TSYN_659",
"ETH_SYS_TSYN_711"
]
}
},
"priority": {
"type": "array",
"items": {
"type": "integer",
"enum": [1, 2, 3, 4]
}
},
"testType": {
"type": "string",
"enum": [
"Resource Usage Evaluation",
"Requirements-based test",
"Interface test",
"Fault injection test",
"Verification of the control flow and data flow",
"Experience testing"
]
},
"status": {
"type": "string",
"enum": [
"Concept",
"Design",
"Deleted"
]
}
},
"additionalProperties": true
}