diff --git a/test/JPP_TestUsecases.csv b/test/JPP_TestUsecases.csv
index be497a24..ceeb504c 100644
--- a/test/JPP_TestUsecases.csv
+++ b/test/JPP_TestUsecases.csv
@@ -3,83 +3,22 @@ TESTID|SECTION|SUBSECTION|DESCRIPTION
JPP_0001|DATA_TYPES|GOODCASE|JSON file with parameters of different data types (basic and composite)
JPP_0002|DATA_TYPES|GOODCASE|JSON file containing parameters with dollar operator syntax at right hand side of colon, basic data types
JPP_0003|DATA_TYPES|GOODCASE|JSON file containing parameters with dollar operator syntax at right hand side of colon, composite data type: list
-JPP_0004|DATA_TYPES|GOODCASE|JSON file containing parameters with dollar operator syntax at right hand side of colon, composite data type: dict
-JPP_0005|DATA_TYPES|GOODCASE|JSON file with string values containing dollar operators
JPP_0100|DATA_INTEGRITY|GOODCASE|JSON file is empty (single pair of brackets only)
JPP_0101|DATA_INTEGRITY|GOODCASE|JSON file with string containing several separator characters and blanks; no parameters
JPP_0102|DATA_INTEGRITY|GOODCASE|JSON file with string containing more special characters, masked special characters and escape sequences
JPP_0200|PARAMETER_SUBSTITUTION|GOODCASE|JSON file with nested parameter / string parameter substitution in parameter value
JPP_0201|PARAMETER_SUBSTITUTION|GOODCASE|JSON file with nested parameter / string parameter substitution in parameter name
-JPP_0202|PARAMETER_SUBSTITUTION|GOODCASE|JSON file with nested parameter / index parameter substitution in parameter name / standard notation
-JPP_0203|PARAMETER_SUBSTITUTION|GOODCASE|JSON file with nested parameter / index parameter substitution in parameter name / dotdict notation
-JPP_0204|PARAMETER_SUBSTITUTION|GOODCASE|JSON file with nested parameter / index parameter substitution in parameter value / standard notation
-JPP_0205|PARAMETER_SUBSTITUTION|GOODCASE|JSON file with nested parameter / index parameter substitution in parameter value / dotdict notation
-JPP_0206|PARAMETER_SUBSTITUTION|GOODCASE|JSON file with nested parameter / key parameter substitution in parameter name / standard notation
-JPP_0207|PARAMETER_SUBSTITUTION|GOODCASE|JSON file with nested parameter / key parameter substitution in parameter name / dotdict notation
-JPP_0208|PARAMETER_SUBSTITUTION|GOODCASE|JSON file with nested parameter / key parameter substitution in parameter value / standard notation
-JPP_0209|PARAMETER_SUBSTITUTION|GOODCASE|JSON file with nested parameter / key parameter substitution in parameter value / dotdict notation
JPP_0250|PARAMETER_SUBSTITUTION|BADCASE|JSON file with nested parameter / string parameter substitution in parameter value / innermost parameter not existing
JPP_0251|PARAMETER_SUBSTITUTION|BADCASE|JSON file with nested parameter / string parameter substitution in parameter name / in between parameter not existing
-JPP_0252|PARAMETER_SUBSTITUTION|BADCASE|JSON file with nested parameter / index parameter substitution in parameter name / standard notation / index parameter not existing
JPP_0253|PARAMETER_SUBSTITUTION|BADCASE|JSON file with nested parameter / index parameter substitution in parameter name / dotdict notation / index parameter not existing
-JPP_0254|PARAMETER_SUBSTITUTION|BADCASE|JSON file with nested parameter / index parameter substitution in parameter value / standard notation / index parameter not existing
JPP_0255|PARAMETER_SUBSTITUTION|BADCASE|JSON file with nested parameter / index parameter substitution in parameter value / dotdict notation / index parameter not existing
-JPP_0256|PARAMETER_SUBSTITUTION|BADCASE|JSON file with nested parameter / key parameter substitution in parameter name / standard notation / variant number not existing
JPP_0257|PARAMETER_SUBSTITUTION|BADCASE|JSON file with nested parameter / key parameter substitution in parameter name / dotdict notation / milestone number not existing
-JPP_0258|PARAMETER_SUBSTITUTION|BADCASE|JSON file with nested parameter / key parameter substitution in parameter value / standard notation / variant number not existing
JPP_0259|PARAMETER_SUBSTITUTION|BADCASE|JSON file with nested parameter / key parameter substitution in parameter value / dotdict notation / milestone number not existing
-JPP_0260|PARAMETER_SUBSTITUTION|BADCASE|JSON file with list parameter substitution in parameter name (composite data types not allowed in names) / (1)
-JPP_0261|PARAMETER_SUBSTITUTION|BADCASE|JSON file with list parameter substitution in parameter name (composite data types not allowed in names) / (2)
-JPP_0262|PARAMETER_SUBSTITUTION|BADCASE|JSON file with dictionary parameter substitution in parameter name (composite data types not allowed in names) / (1)
-JPP_0263|PARAMETER_SUBSTITUTION|BADCASE|JSON file with dictionary parameter substitution in parameter name (composite data types not allowed in names) / (2)
-JPP_0264|PARAMETER_SUBSTITUTION|BADCASE|JSON file with list parameter substitution in key name (composite data types not allowed in names) / (1)
-JPP_0265|PARAMETER_SUBSTITUTION|BADCASE|JSON file with list parameter substitution in key name (composite data types not allowed in names) / (2)
-JPP_0266|PARAMETER_SUBSTITUTION|BADCASE|JSON file with dictionary parameter substitution in key name (composite data types not allowed in names) / (1)
-JPP_0267|PARAMETER_SUBSTITUTION|BADCASE|JSON file with dictionary parameter substitution in key name (composite data types not allowed in names) / (2)
JPP_0300|VALUE_DETECTION|GOODCASE|JSON file with parameter of type 'list' / index (in square brackets) defined outside the curly brackets (valid syntax)
-JPP_0301|VALUE_DETECTION|GOODCASE|JSON file with expression containing more closing elements '}' than opening elements '${' (valid syntax)
-JPP_0302|VALUE_DETECTION|GOODCASE|JSON file with expression starting with '${' and ending with '}' / no further matching '${' and '}' in between (valid syntax)
-JPP_0303|VALUE_DETECTION|GOODCASE|JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (nested) (valid syntax)
-JPP_0304|VALUE_DETECTION|GOODCASE|JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (not all nested) (valid syntax)
-JPP_0350|VALUE_DETECTION|BADCASE|JSON file with parameter of type 'list' / index (in square brackets) defined inside the curly brackets (invalid syntax 1)
-JPP_0351|VALUE_DETECTION|BADCASE|JSON file with parameter of type 'list' / index (in square brackets) defined inside the curly brackets (invalid syntax 2)
-JPP_0352|VALUE_DETECTION|BADCASE|JSON file with parameter of type 'list' / index (in square brackets) defined inside the curly brackets (invalid syntax 3)
-JPP_0353|VALUE_DETECTION|BADCASE|JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 1)
-JPP_0354|VALUE_DETECTION|BADCASE|JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 2)
-JPP_0355|VALUE_DETECTION|BADCASE|JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 3)
-JPP_0356|VALUE_DETECTION|BADCASE|JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 4)
-JPP_0357|VALUE_DETECTION|BADCASE|JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 5)
-JPP_0358|VALUE_DETECTION|BADCASE|JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 6)
-JPP_0359|VALUE_DETECTION|BADCASE|JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 6)
-JPP_0360|VALUE_DETECTION|BADCASE|JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 9)
JPP_0361|VALUE_DETECTION|BADCASE|JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 1)
-JPP_0362|VALUE_DETECTION|BADCASE|JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 2)
-JPP_0363|VALUE_DETECTION|BADCASE|JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 3)
-JPP_0364|VALUE_DETECTION|BADCASE|JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 4)
-JPP_0365|VALUE_DETECTION|BADCASE|JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 5)
-JPP_0366|VALUE_DETECTION|BADCASE|JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 6)
-JPP_0367|VALUE_DETECTION|BADCASE|JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (not all nested) (invalid syntax 1)
-JPP_0368|VALUE_DETECTION|BADCASE|JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (not all nested) (invalid syntax 2)
-JPP_0369|VALUE_DETECTION|BADCASE|JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (not all nested) (invalid syntax 3)
-JPP_0370|VALUE_DETECTION|BADCASE|JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (not all nested) (invalid syntax 4)
-JPP_0371|VALUE_DETECTION|BADCASE|JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (not all nested) (invalid syntax 5)
-JPP_0450|NAMING_CONVENTION|BADCASE|JSON file with Python keywords used as parameter names (1)
-JPP_0451|NAMING_CONVENTION|BADCASE|JSON file with Python keywords used as parameter names (2)
-JPP_0452|NAMING_CONVENTION|BADCASE|JSON file with Python keywords used as parameter names (3)
-JPP_0453|NAMING_CONVENTION|BADCASE|JSON file with Python keywords used as parameter names (4)
-JPP_0454|NAMING_CONVENTION|BADCASE|JSON file with Python keywords used as parameter names (5)
-JPP_0455|NAMING_CONVENTION|BADCASE|JSON file with Python keywords used as parameter names (6)
-JPP_0456|NAMING_CONVENTION|BADCASE|JSON file with Python keywords used as parameter names (7)
-JPP_0457|NAMING_CONVENTION|BADCASE|JSON file with Python keywords used as parameter names (8)
-JPP_0458|NAMING_CONVENTION|BADCASE|JSON file with parameter name containing not allowed special characters
JPP_0500|COMPOSITE_EXPRESSIONS|GOODCASE|JSON file with composite data structure (nested lists and dictionaries 1)
-JPP_0501|COMPOSITE_EXPRESSIONS|GOODCASE|JSON file with composite data structure (nested lists and dictionaries 2)
JPP_0502|COMPOSITE_EXPRESSIONS|GOODCASE|JSON file with composite data structure (nested lists and dictionaries 3 / some key names with dots inside)
-JPP_0503|COMPOSITE_EXPRESSIONS|GOODCASE|JSON file with composite data structure (some lists)
-JPP_0504|COMPOSITE_EXPRESSIONS|GOODCASE|JSON file with composite data structure (some dictionaries)
-JPP_0505|COMPOSITE_EXPRESSIONS|GOODCASE|JSON file with composite strings containing several times a colon and a comma (JSON syntax elements)
JPP_0506|COMPOSITE_EXPRESSIONS|GOODCASE|JSON file with composite strings containing several combinations of curly brackets and special characters before
-JPP_0550|COMPOSITE_EXPRESSIONS|BADCASE|JSON file with composite data structure (nested lists and dictionaries / some key names with dots inside)
JPP_0900|COMMON_SYNTAX_VIOLATIONS|GOODCASE|JSON file with syntax error, that is commented out
JPP_0950|COMMON_SYNTAX_VIOLATIONS|BADCASE|JSON file with syntax error (1)
JPP_0951|COMMON_SYNTAX_VIOLATIONS|BADCASE|JSON file with syntax error (2)
diff --git a/test/JPP_TestUsecases.html b/test/JPP_TestUsecases.html
index 07e073a8..89bae9ae 100644
--- a/test/JPP_TestUsecases.html
+++ b/test/JPP_TestUsecases.html
@@ -136,1965 +136,25 @@
-JPP_0004
- |
-
-
-
-DATA_TYPES
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file containing parameters with dollar operator syntax at right hand side of colon, composite data type: dict
-Expected: All parameters referenced by dollar operator are resolved correctly, with their correct data types
-
-
- |
-
-
-
-
-|
-
-
-5
- |
-
-
-
-
-JPP_0005
- |
-
-
-
-DATA_TYPES
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with string values containing dollar operators
-Expected: All parameters referenced by dollar operator are resolved correctly, outcome is a string containing the values of all referenced parameters
-
-
- |
-
-
-
-
-|
-
-
-6
- |
-
-
-
-
-JPP_0100
- |
-
-
-
-DATA_INTEGRITY
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file is empty (single pair of brackets only)
-Expected: JsonPreprocessor returns empty dictionary
-
-
- |
-
-
-
-
-|
-
-
-7
- |
-
-
-
-
-JPP_0101
- |
-
-
-
-DATA_INTEGRITY
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with string containing several separator characters and blanks; no parameters
-Expected: String is returned unchanged
-
-
- |
-
-
-
-
-|
-
-
-8
- |
-
-
-
-
-JPP_0102
- |
-
-
-
-DATA_INTEGRITY
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with string containing more special characters, masked special characters and escape sequences
-Expected: String is returned unchanged (but with masked special characters and escape sequences resolved)
-
-
- |
-
-
-
-
-|
-
-
-9
- |
-
-
-
-
-JPP_0200
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with nested parameter / string parameter substitution in parameter value
-Expected: JsonPreprocessor creates a new string with all dollar operator expressions resolved as string
-
-
- |
-
-
-
-
-|
-
-
-10
- |
-
-
-
-
-JPP_0201
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with nested parameter / string parameter substitution in parameter name
-Expected: JsonPreprocessor creates a new string with all dollar operator expressions resolved as string
-
-
- |
-
-
-
-
-|
-
-
-11
- |
-
-
-
-
-JPP_0202
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with nested parameter / index parameter substitution in parameter name / standard notation
-Expected: JsonPreprocessor creates a new string with all dollar operator expressions resolved as string
-
-
- |
-
-
-
-
-|
-
-
-12
- |
-
-
-
-
-JPP_0203
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with nested parameter / index parameter substitution in parameter name / dotdict notation
-Expected: JsonPreprocessor creates a new string with all dollar operator expressions resolved as string
-
-
- |
-
-
-
-
-|
-
-
-13
- |
-
-
-
-
-JPP_0204
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with nested parameter / index parameter substitution in parameter value / standard notation
-Expected: JsonPreprocessor creates a new string with all dollar operator expressions resolved as string
-
-
- |
-
-
-
-
-|
-
-
-14
- |
-
-
-
-
-JPP_0205
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with nested parameter / index parameter substitution in parameter value / dotdict notation
-Expected: JsonPreprocessor creates a new string with all dollar operator expressions resolved as string
-
-
- |
-
-
-
-
-|
-
-
-15
- |
-
-
-
-
-JPP_0206
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with nested parameter / key parameter substitution in parameter name / standard notation
-Expected: JsonPreprocessor creates a new string with all dollar operator expressions resolved as string
-
-
- |
-
-
-
-
-|
-
-
-16
- |
-
-
-
-
-JPP_0207
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with nested parameter / key parameter substitution in parameter name / dotdict notation
-Expected: JsonPreprocessor creates a new string with all dollar operator expressions resolved as string
-
-
- |
-
-
-
-
-|
-
-
-17
- |
-
-
-
-
-JPP_0208
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with nested parameter / key parameter substitution in parameter value / standard notation
-Expected: JsonPreprocessor creates a new string with all dollar operator expressions resolved as string
-
-
- |
-
-
-
-
-|
-
-
-18
- |
-
-
-
-
-JPP_0209
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with nested parameter / key parameter substitution in parameter value / dotdict notation
-Expected: JsonPreprocessor creates a new string with all dollar operator expressions resolved as string
-
-
- |
-
-
-
-
-|
-
-
-19
- |
-
-
-
-
-JPP_0250
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with nested parameter / string parameter substitution in parameter value / innermost parameter not existing
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-20
- |
-
-
-
-
-JPP_0251
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with nested parameter / string parameter substitution in parameter name / in between parameter not existing
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-21
- |
-
-
-
-
-JPP_0252
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with nested parameter / index parameter substitution in parameter name / standard notation / index parameter not existing
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-22
- |
-
-
-
-
-JPP_0253
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with nested parameter / index parameter substitution in parameter name / dotdict notation / index parameter not existing
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-23
- |
-
-
-
-
-JPP_0254
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with nested parameter / index parameter substitution in parameter value / standard notation / index parameter not existing
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-24
- |
-
-
-
-
-JPP_0255
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with nested parameter / index parameter substitution in parameter value / dotdict notation / index parameter not existing
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-25
- |
-
-
-
-
-JPP_0256
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with nested parameter / key parameter substitution in parameter name / standard notation / variant number not existing
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-26
- |
-
-
-
-
-JPP_0257
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with nested parameter / key parameter substitution in parameter name / dotdict notation / milestone number not existing
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-27
- |
-
-
-
-
-JPP_0258
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with nested parameter / key parameter substitution in parameter value / standard notation / variant number not existing
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-28
- |
-
-
-
-
-JPP_0259
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with nested parameter / key parameter substitution in parameter value / dotdict notation / milestone number not existing
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-29
- |
-
-
-
-
-JPP_0260
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with list parameter substitution in parameter name (composite data types not allowed in names) / (1)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-30
- |
-
-
-
-
-JPP_0261
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with list parameter substitution in parameter name (composite data types not allowed in names) / (2)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-31
- |
-
-
-
-
-JPP_0262
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with dictionary parameter substitution in parameter name (composite data types not allowed in names) / (1)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-32
- |
-
-
-
-
-JPP_0263
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with dictionary parameter substitution in parameter name (composite data types not allowed in names) / (2)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-33
- |
-
-
-
-
-JPP_0264
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with list parameter substitution in key name (composite data types not allowed in names) / (1)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-34
- |
-
-
-
-
-JPP_0265
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with list parameter substitution in key name (composite data types not allowed in names) / (2)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-35
- |
-
-
-
-
-JPP_0266
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with dictionary parameter substitution in key name (composite data types not allowed in names) / (1)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-36
- |
-
-
-
-
-JPP_0267
- |
-
-
-
-PARAMETER_SUBSTITUTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with dictionary parameter substitution in key name (composite data types not allowed in names) / (2)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
- |
-
-
-
-
-|
-
-
-37
- |
-
-
-
-
-JPP_0300
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with parameter of type 'list' / index (in square brackets) defined outside the curly brackets (valid syntax)
-Expected: JsonPreprocessor returns values
-
-
-Checklist rule 1
- |
-
-
-
-
-|
-
-
-38
- |
-
-
-
-
-JPP_0301
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with expression containing more closing elements '}' than opening elements '${' (valid syntax)
-Expected: JsonPreprocessor returns values
-
-
-Checklist rule 3
- |
-
-
-
-
-|
-
-
-39
- |
-
-
-
-
-JPP_0302
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with expression starting with '${' and ending with '}' / no further matching '${' and '}' in between (valid syntax)
-Expected: JsonPreprocessor returns values
-
-
-Checklist rule 4
- |
-
-
-
-
-|
-
-
-40
- |
-
-
-
-
-JPP_0303
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (nested) (valid syntax)
-Expected: JsonPreprocessor returns values
-
-
-Checklist rule 5
- |
-
-
-
-
-|
-
-
-41
- |
-
-
-
-
-JPP_0304
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (not all nested) (valid syntax)
-Expected: JsonPreprocessor returns values
-
-
-Checklist rule 6
- |
-
-
-
-
-|
-
-
-42
- |
-
-
-
-
-JPP_0350
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with parameter of type 'list' / index (in square brackets) defined inside the curly brackets (invalid syntax 1)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 1 / pattern 1
- |
-
-
-
-
-|
-
-
-43
- |
-
-
-
-
-JPP_0351
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with parameter of type 'list' / index (in square brackets) defined inside the curly brackets (invalid syntax 2)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 1 / pattern 2
- |
-
-
-
-
-|
-
-
-44
- |
-
-
-
-
-JPP_0352
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with parameter of type 'list' / index (in square brackets) defined inside the curly brackets (invalid syntax 3)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 1 / pattern 3
- |
-
-
-
-
-|
-
-
-45
- |
-
-
-
-
-JPP_0353
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 1)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 2 / pattern 1
- |
-
-
-
-
-|
-
-
-46
- |
-
-
-
-
-JPP_0354
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 2)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 2 / pattern 2
- |
-
-
-
-
-|
-
-
-47
- |
-
-
-
-
-JPP_0355
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 3)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 2 / pattern 3
- |
-
-
-
-
-|
-
-
-48
- |
-
-
-
-
-JPP_0356
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 4)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 2 / pattern 4
- |
-
-
-
-
-|
-
-
-49
- |
-
-
-
-
-JPP_0357
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 5)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 2 / pattern 5
- |
-
-
-
-
-|
-
-
-50
- |
-
-
-
-
-JPP_0358
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 6)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 2 / pattern 6
- |
-
-
-
-
-|
-
-
-51
- |
-
-
-
-
-JPP_0359
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 6)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 2 / pattern 7
- |
-
-
-
-
-|
-
-
-52
- |
-
-
-
-
-JPP_0360
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more opening elements '${' than closing elements '}' (invalid syntax 9)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 2 / pattern 8
- |
-
-
-
-
-|
-
-
-53
- |
-
-
-
-
-JPP_0361
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 1)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 3 / pattern 1
- |
-
-
-
-
-|
-
-
-54
- |
-
-
-
-
-JPP_0362
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 2)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 3 / pattern 2
- |
-
-
-
-
-|
-
-
-55
- |
-
-
-
-
-JPP_0363
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 3)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 3 / pattern 3
- |
-
-
-
-
-|
-
-
-56
- |
-
-
-
-
-JPP_0364
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 4)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 3 / pattern 4
- |
-
-
-
-
-|
-
-
-57
- |
-
-
-
-
-JPP_0365
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 5)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 3 / pattern 5
- |
-
-
-
-
-|
-
-
-58
- |
-
-
-
-
-JPP_0366
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 6)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 3 / pattern 6
- |
-
-
-
-
-|
-
-
-59
- |
-
-
-
-
-JPP_0367
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (not all nested) (invalid syntax 1)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 6 / pattern 1
- |
-
-
-
-
-|
-
-
-60
- |
-
-
-
-
-JPP_0368
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (not all nested) (invalid syntax 2)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 6 / pattern 2
- |
-
-
-
-
-|
-
-
-61
- |
-
-
-
-
-JPP_0369
+JPP_0100
|
-VALUE_DETECTION
+DATA_INTEGRITY
|
-
-BADCASE
+
+GOODCASE
|
-JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (not all nested) (invalid syntax 3)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-
-Checklist rule 6 / pattern 3
- |
-
-
-
-
-|
-
-
-62
- |
-
-
-
-
-JPP_0370
- |
-
-
-
-VALUE_DETECTION
- |
-
-
-
-BADCASE
- |
+JSON file is empty (single pair of brackets only)
+Expected: JsonPreprocessor returns empty dictionary
-
-
-JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (not all nested) (invalid syntax 4)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-Checklist rule 6 / pattern 4
|
@@ -2103,32 +163,31 @@
-63
+5
|
-JPP_0371
+JPP_0101
|
-VALUE_DETECTION
+DATA_INTEGRITY
|
-
-BADCASE
+
+GOODCASE
|
-JSON file with expression starting with '${' and ending with '}', further matching '${' and '}' in between (not all nested) (invalid syntax 5)
-Expected: No values are returned, and JsonPreprocessor throws an exception
+JSON file with string containing several separator characters and blanks; no parameters
+Expected: String is returned unchanged
+
-
-Checklist rule 6 / pattern 5
|
@@ -2137,29 +196,29 @@
-64
+6
|
-JPP_0450
+JPP_0102
|
-NAMING_CONVENTION
+DATA_INTEGRITY
|
-
-BADCASE
+
+GOODCASE
|
-JSON file with Python keywords used as parameter names (1)
-Expected: No values are returned, and JsonPreprocessor throws an exception
+JSON file with string containing more special characters, masked special characters and escape sequences
+Expected: String is returned unchanged (but with masked special characters and escape sequences resolved)
|
@@ -2170,29 +229,29 @@
-65
+7
|
-JPP_0451
+JPP_0200
|
-NAMING_CONVENTION
+PARAMETER_SUBSTITUTION
|
-
-BADCASE
+
+GOODCASE
|
-JSON file with Python keywords used as parameter names (2)
-Expected: No values are returned, and JsonPreprocessor throws an exception
+JSON file with nested parameter / string parameter substitution in parameter value
+Expected: JsonPreprocessor creates a new string with all dollar operator expressions resolved as string
|
@@ -2203,29 +262,29 @@
-66
+8
|
-JPP_0452
+JPP_0201
|
-NAMING_CONVENTION
+PARAMETER_SUBSTITUTION
|
-
-BADCASE
+
+GOODCASE
|
-JSON file with Python keywords used as parameter names (3)
-Expected: No values are returned, and JsonPreprocessor throws an exception
+JSON file with nested parameter / string parameter substitution in parameter name
+Expected: JsonPreprocessor creates a new string with all dollar operator expressions resolved as string
|
@@ -2236,18 +295,18 @@
-67
+9
|
-JPP_0453
+JPP_0250
|
-NAMING_CONVENTION
+PARAMETER_SUBSTITUTION
|
@@ -2257,7 +316,7 @@
|
-JSON file with Python keywords used as parameter names (4)
+JSON file with nested parameter / string parameter substitution in parameter value / innermost parameter not existing
Expected: No values are returned, and JsonPreprocessor throws an exception
@@ -2269,18 +328,18 @@
|
-68
+10
|
-JPP_0454
+JPP_0251
|
-NAMING_CONVENTION
+PARAMETER_SUBSTITUTION
|
@@ -2290,7 +349,7 @@
|
-JSON file with Python keywords used as parameter names (5)
+JSON file with nested parameter / string parameter substitution in parameter name / in between parameter not existing
Expected: No values are returned, and JsonPreprocessor throws an exception
@@ -2302,18 +361,18 @@
|
-69
+11
|
-JPP_0455
+JPP_0253
|
-NAMING_CONVENTION
+PARAMETER_SUBSTITUTION
|
@@ -2323,7 +382,7 @@
|
-JSON file with Python keywords used as parameter names (6)
+JSON file with nested parameter / index parameter substitution in parameter name / dotdict notation / index parameter not existing
Expected: No values are returned, and JsonPreprocessor throws an exception
@@ -2335,18 +394,18 @@
|
-70
+12
|
-JPP_0456
+JPP_0255
|
-NAMING_CONVENTION
+PARAMETER_SUBSTITUTION
|
@@ -2356,7 +415,7 @@
|
-JSON file with Python keywords used as parameter names (7)
+JSON file with nested parameter / index parameter substitution in parameter value / dotdict notation / index parameter not existing
Expected: No values are returned, and JsonPreprocessor throws an exception
@@ -2368,18 +427,18 @@
|
-71
+13
|
-JPP_0457
+JPP_0257
|
-NAMING_CONVENTION
+PARAMETER_SUBSTITUTION
|
@@ -2389,7 +448,7 @@
|
-JSON file with Python keywords used as parameter names (8)
+JSON file with nested parameter / key parameter substitution in parameter name / dotdict notation / milestone number not existing
Expected: No values are returned, and JsonPreprocessor throws an exception
@@ -2401,18 +460,18 @@
|
-72
+14
|
-JPP_0458
+JPP_0259
|
-NAMING_CONVENTION
+PARAMETER_SUBSTITUTION
|
@@ -2422,7 +481,7 @@
|
-JSON file with parameter name containing not allowed special characters
+JSON file with nested parameter / key parameter substitution in parameter value / dotdict notation / milestone number not existing
Expected: No values are returned, and JsonPreprocessor throws an exception
@@ -2434,18 +493,18 @@
|
-73
+15
|
-JPP_0500
+JPP_0300
|
-COMPOSITE_EXPRESSIONS
+VALUE_DETECTION
|
@@ -2455,11 +514,11 @@
|
-JSON file with composite data structure (nested lists and dictionaries 1)
-Expected: JsonPreprocessor returns expected value
+JSON file with parameter of type 'list' / index (in square brackets) defined outside the curly brackets (valid syntax)
+Expected: JsonPreprocessor returns values
-Standard notation
+Checklist rule 1
|
@@ -2468,32 +527,32 @@
-74
+16
|
-JPP_0501
+JPP_0361
|
-COMPOSITE_EXPRESSIONS
+VALUE_DETECTION
|
-
-GOODCASE
+
+BADCASE
|
-JSON file with composite data structure (nested lists and dictionaries 2)
-Expected: JsonPreprocessor returns expected value
+JSON file with expression containing more closing elements '}' than opening elements '${' (invalid syntax 1)
+Expected: No values are returned, and JsonPreprocessor throws an exception
-Dotdict notation
+Checklist rule 3 / pattern 1
|
@@ -2502,13 +561,13 @@
-75
+17
|
-JPP_0502
+JPP_0500
|
@@ -2523,7 +582,7 @@
|
-JSON file with composite data structure (nested lists and dictionaries 3 / some key names with dots inside)
+JSON file with composite data structure (nested lists and dictionaries 1)
Expected: JsonPreprocessor returns expected value
@@ -2536,79 +595,13 @@
|
-76
- |
-
-
-
-
-JPP_0503
- |
-
-
-
-COMPOSITE_EXPRESSIONS
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with composite data structure (some lists)
-Expected: JsonPreprocessor returns expected value
-
-
- |
-
-
-
-
-|
-
-
-77
- |
-
-
-
-
-JPP_0504
- |
-
-
-
-COMPOSITE_EXPRESSIONS
- |
-
-
-
-GOODCASE
- |
-
-
-
-JSON file with composite data structure (some dictionaries)
-Expected: JsonPreprocessor returns expected value
-
-
- |
-
-
-
-
-|
-
-
-78
+18
|
-JPP_0505
+JPP_0502
|
@@ -2623,10 +616,11 @@
|
-JSON file with composite strings containing several times a colon and a comma (JSON syntax elements)
+JSON file with composite data structure (nested lists and dictionaries 3 / some key names with dots inside)
Expected: JsonPreprocessor returns expected value
-
+
+Standard notation
|
@@ -2635,7 +629,7 @@
-79
+19
|
@@ -2668,42 +662,7 @@
|
-80
- |
-
-
-
-
-JPP_0550
- |
-
-
-
-COMPOSITE_EXPRESSIONS
- |
-
-
-
-BADCASE
- |
-
-
-
-JSON file with composite data structure (nested lists and dictionaries / some key names with dots inside)
-Expected: No values are returned, and JsonPreprocessor throws an exception
-
-Needs clarification!
-
-Dotdict notation (ambiguous in this case)
- |
-
-
-
-
-|
-
-
-81
+20
|
@@ -2736,7 +695,7 @@
|
-82
+21
|
@@ -2769,7 +728,7 @@
|
-83
+22
|
@@ -2802,7 +761,7 @@
|
-84
+23
|
@@ -2835,7 +794,7 @@
|
-85
+24
|
@@ -2868,7 +827,7 @@
|
-86
+25
|
@@ -2901,7 +860,7 @@
-Generated: 02.08.2023 - 14:43:07
+Generated: 09.08.2023 - 11:47:23
|