CSD02 mandatory tests

[domachine]

This PR includes the additional mandatory tests from CSD02.

• Fixes minimalSecurityAdvisoryDoc.js and minimalVexDoc.js invalid #4
• Fixes Adopt 6.1.21 #7

[tschmidtb51]

@domachine Do you have a small script that imports the library and validates a file against one test? That would help me to test some edge cases of the implementation.

Just from looking at the code I couldn't spot anything obvious...

[domachine]

@domachine Do you have a small script that imports the library and validates a file against one test? That would help me to test some edge cases of the implementation.

Just from looking at the code I couldn't spot anything obvious...

Yes, I can throw one together. But if you want, you could add these edge cases to the documentTests.js file to include them in the test-suite. Just copy and paste the JSON into the content field. Since JSON is also valid JS, no changes are needed.

[tschmidtb51]

Yes, I can throw one together.

I wouldn't mind if you could do that. I would like to use that in the TC's repo to make sure the example files fail the right tests...

[domachine]

Yes, I can throw one together.

I wouldn't mind if you could do that. I would like to use that in the TC's repo to make sure the example files fail the right tests...

Here is a git-patch. Save it on your disk and run git apply <patch-file-path> from within the csaf-validator-lib repo. Then you can run the script using the following command: ./scripts/runTest.js <doc-file> mandatoryTest_6_1_1. mandatoryTest_6_1_1 is a sample here. You can insert any test name from lib/mandatoryTests.js, lib/optionalTests.js, lib/schemaTests.js and lib/schemaTests.js.

run_test_script.patch

[tschmidtb51]

Please see my comments.

[domachine]

Alright I addressed the issues and rebased the history.

[tschmidtb51]

Just a minor wording change suggested...

[domachine]

Just a minor wording change suggested...

Fixed 🙂

[tschmidtb51]

LGTM