You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add new line(s) for test cases to `src/test/resources/features/validate.feature`: (NOTE: This feature file is organized by minor versions, 15.2.x, 15.3.x, etc. based upon the next expected minor version. If the next minor version is not included create a new section of the document. Contact Jordan for more details if needed.)
33
33
*
34
34
***testId** - this should be the GitHub reference to the applicable Github ticket. For this use case, that should be set to `NASA-PDS/pds4-information-model#753`
35
35
***testName** - title for the test that would be useful from someone trying to review a test plan with that title. For this use case, that should be set to `My test for new Current units nA, microA`
36
36
***testDir** - directory under `odel-lddtool/src/test/resources/` where your test data exists. For this use case, that should be set to `github753b`
37
37
***messageCount** - number of expected errors or warnings. For this use case, that should be set to `0` (success).
38
-
***messageText** - the expected output should match very closely to messageCount, e.g. `4 errors expected`, `8 warnings expected` (not sure how this is really used or why we have this right now...). For this use case, that should be set to `0 errors expected` (success).
39
-
***problemEnum** - `totalErrors`, `totalWarnings`, or specific error you expect from validate output. For this use case, that should be set to `SCHEMATRON_ERROR`
38
+
***problemEnum** - `totalErrors`, `totalWarnings`, or specific error you expect from validate output. For this use case, that should be set to `totalErrors`
40
39
* for specific error, search [Validate ProblemTypes](https://github.com/NASA-PDS/validate/blob/main/src/main/java/gov/nasa/pds/tools/validate/ProblemType.java) for the error identifier, and put the ALL CAPS value in the file, e.g. for `error.label.schematron`, if I search the file I see this line `SCHEMATRON_ERROR("error.label.schematron")`, so the problemEnum value == `SCHEMATRON_ERROR`
41
40
***commandArgs** - these are the Validate Tool command-line arguments. For this example, let's set the target directory `--target {resourceDir}/github753/pc__d139.xml`. By default, the following are already included for validate under the hood of the test code:
42
41
*`--disable-context-mismatch-warnings`
43
42
*`--report-style json`
44
-
*`--skip-content-validation`
43
+
*`--skip-content-validation` (unless `enableContentValidation` is set to `"true"`)
44
+
*`--skip-context-validation`
45
45
*`--report-file {reportDir}/...`
46
46
***ingestLDDFileName** - the IngestLDD filenames you would like to have LDDTool generate the schema/schmematron for testing. These files should be in the test directory created earlier.
47
+
***pds4Version** - the PDS4 Information Model version to use (e.g., `"1C00"`, `"1D00"`). Leave empty (`""`) to use the latest version.
48
+
***enableContentValidation** - set to `"true"` to enable content validation for this test case (e.g., when testing table content validation). Default is `"false"`.
47
49
* Now run the test(s):
48
50
* Via Eclipse: right-click `Run as` -> `Cucumber Feature`
49
51
* Via Maven (replace with applicable tag for this build):
0 commit comments