-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Broken test data in valid-bom-1.x.json #296
Comments
@jkowalleck, sure, I'm trying to figure out how to fix this in the textproto files. If I understand correctly there is no null value in textproto. So, I will have to take the second approach for the textproto files. |
the properties you are referring to are defined non-nullable, but optional. |
Fix test data inconsistency regarding encoding of license content in `valid-bom` fixes #296 Signed-off-by: tokcum <[email protected]>
Fix test data inconsistency regarding encoding of license content in `valid-bom` fixes CycloneDX#296 Signed-off-by: tokcum <[email protected]>
forward-port of CycloneDX#299 fixes CycloneDX#296 in 1.6 Signed-off-by: Jan Kowalleck <[email protected]>
Hi,
working on cyclonedx-rust-cargo to support 1.4, I'm experiencing failed integration tests when verifying against valid-bom test data.
In valid-bom-1.[2-5].json and valid-bom-1.[3-5].textproto, it's stated that the Apache 2.0 is base64 encoded, see encoding. However, the provided string in content is plain ASCII, see code snippet below.
This breaks the integration tests at cyclonedx-rust-cargo.
The XML files are not affected. There, content is a base64 encoded string.
We have two options to fix this: either set the encoding to null or provide a base64 encoded string in content. I prefer the first approach because it keeps the test data more concise and these test files are not for testing license encoding but overall validity of a BOM.
Broken example:
Working example (1):
Working example (2), license string taken from valid-bom-1.4.xml:
The text was updated successfully, but these errors were encountered: