Skip to content
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

test(COD-4237): only check if the list of expected is not 0 #206

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

jeremydubreil
Copy link
Contributor

@jeremydubreil jeremydubreil commented Nov 20, 2024

The SCA scan now finds one less finding than before on the test code.

@jeremydubreil jeremydubreil changed the title test(COD-3861): update the list of expected output test: update the list of expected output Nov 20, 2024
@jeremydubreil jeremydubreil marked this pull request as ready for review November 20, 2024 14:52
@jeremydubreil jeremydubreil marked this pull request as draft November 20, 2024 14:53
@jeremydubreil jeremydubreil force-pushed the update-expected-output branch from 225f8b1 to 92da6b6 Compare January 28, 2025 20:38
@jeremydubreil jeremydubreil changed the title test: update the list of expected output test(COD-4237): update the list of expected output Jan 28, 2025
@jeremydubreil jeremydubreil marked this pull request as ready for review January 28, 2025 21:06
@jeremydubreil jeremydubreil requested a review from a team January 29, 2025 09:21
@@ -60,7 +60,7 @@ jobs:
working-directory: artifact
run: |
export SCA_RESULTS=`jq '.runs | map (.results | length) | add' sca.sarif`
expectedScaResults=5
expectedScaResults=4

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we leave this as an exact number instead of following the codesec approach that checks whether the expectedScaResults is just not 0?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we can do that in case the number of vulns reported is changing again. We did like that in the past to check that both SCA and SAST are working as expected.

@jeremydubreil jeremydubreil force-pushed the update-expected-output branch from 92da6b6 to 32a0f8f Compare January 29, 2025 10:47
@jeremydubreil jeremydubreil changed the title test(COD-4237): update the list of expected output test(COD-4237): only check if the list of expected is not 0 Jan 29, 2025
Copy link

@baltoiteodor baltoiteodor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jeremydubreil jeremydubreil force-pushed the update-expected-output branch from 32a0f8f to 6db386e Compare January 29, 2025 11:47
@jeremydubreil jeremydubreil merged commit c06a22a into main Jan 29, 2025
3 checks passed
@jeremydubreil jeremydubreil deleted the update-expected-output branch January 29, 2025 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants