-
Notifications
You must be signed in to change notification settings - Fork 9
Feat/199 informative tests csaf2.1 6.3.13 #279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Coverage after merging feat/199-Informative-Tests_CSAF2_1_6.3.13 into main
Coverage Report
|
Can you rebase this? |
e82e9de
to
3b6d005
Compare
3b6d005
to
2b5637b
Compare
Coverage after merging feat/199-Informative-Tests_CSAF2_1_6.3.13 into 196-csaf-2.1
Coverage Report
|
2b5637b
to
7a0cb87
Compare
Coverage after merging feat/199-Informative-Tests_CSAF2_1_6.3.13 into 196-csaf-2.1
Coverage Report
|
7a0cb87
to
26da0cd
Compare
Coverage after merging feat/199-Informative-Tests_CSAF2_1_6.3.13 into 196-csaf-2.1
Coverage Report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where does the implementation cover the part latest decision point version available at the time of the timestamp was used. The test SHALL fail if a later version was used.
?
We should have different errors for both cases (not latest vs. too late resp. wrong timestamp)
metrics: { | ||
elements: { | ||
additionalProperties: true, | ||
properties: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't that be optionalProperties
? I had a chat with @domachine today about the topic and using properties
too early in the chain (or in arrays) will IOHO result in vanishing/flickering errors if a new element is added but not yet filled with any content. Please also change accordingly in other places.
) { | ||
ctx.infos.push({ | ||
instancePath: `/vulnerabilities/${vulnerabilityIndex}/metrics/${metricIndex}/content/ssvc_v1/selections/${selectionIndex}/version`, | ||
message: `ssvc_v1 version '${selection.version}' is not latest decision point version '${latestVersion}'`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The error message is misleading as well - it is all about the decision point (esp. the part ssvc_v1 version '${selection.version}
)
26da0cd
to
8e54cab
Compare
Coverage after merging feat/199-Informative-Tests_CSAF2_1_6.3.13 into main
Coverage Report
|
…ies to properties in input schema
… the supported tests, use types from inputSchema
8e54cab
to
8006afb
Compare
Coverage after merging feat/199-Informative-Tests_CSAF2_1_6.3.13 into main
Coverage Report
|
Script read-ssvc-decision-points.js has to be executed for every deployment