CSAF 2.1 Mandatory test 6.1.14 testcase fails test 6.1.21

[tschmidtb51]

The valid example 2 fails for 6.1.14; the same issue might occur for CSAF 2.0. I guess the second level sorting criteria is not applied.

[rainer-exxcellent]

The valid examples 2 oasis_csaf_tc-csaf_2_0-2021-6-1-14-12.json and oasis_csaf_tc-csaf_2_1-2024-6-1-14-02.json doesn't seem to have changed recently and our automatic test run successfully.
With which version did you test?

[tschmidtb51]

I tested with Secvisogram 2.6.4 and csaf-validator-lib 2.0.26-8-gb33dc46.

I'll report the finding here against CSAF 2.1, it is basically the same against CSAF 2.0, if I haven't overlooked something:

nodejs scripts/runTest.js -t mandatoryTest_6_1_21 -c 2.1 -f csaf/csaf_2.1/test/validator/data/mandatory/oasis_csaf_tc-csaf_2_1-2024-6-1-14-12.json

leads to

{
  "tests": [
    {
      "isValid": false,
      "errors": [
        {
          "instancePath": "/document/tracking/revision_history",
          "message": "revision history does not start with a version of 0 or 1 when sorted by date"
        }
      ],
      "warnings": [],
      "infos": [],
      "name": "mandatoryTest_6_1_21"
    }
  ],
  "isValid": false
}

but

      "revision_history": [
        {
          "date": "2024-01-22T10:00:00.000Z", // ...
        },
        {
          "date": "2024-01-22T10:00:00.000Z", // ...
        }
      ],

both entries have the same date...
Therefore, a second level sorting criteria (number) has to be taken into account.

I'm sorry about the unclear description of the issue.

[tschmidtb51]

@rainer-exxcellent I added a file in f699123 that should aid in detecting this error.