-
Notifications
You must be signed in to change notification settings - Fork 508
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
🌱 use ValidateTestReturn for SAST tests #3872
Merged
spencerschrock
merged 3 commits into
ossf:main
from
spencerschrock:sast-compare-logger-messages
Feb 13, 2024
Merged
🌱 use ValidateTestReturn for SAST tests #3872
spencerschrock
merged 3 commits into
ossf:main
from
spencerschrock:sast-compare-logger-messages
Feb 13, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
previously, we only checked the result score. test failures with this method dont produce as actionable feedback. Signed-off-by: Spencer Schrock <[email protected]>
Signed-off-by: Spencer Schrock <[email protected]>
spencerschrock
requested review from
naveensrinivasan and
laurentsimon
and removed request for
a team
February 12, 2024 21:03
spencerschrock
temporarily deployed
to
gitlab
February 12, 2024 21:03 — with
GitHub Actions
Inactive
spencerschrock
temporarily deployed
to
integration-test
February 12, 2024 21:03 — with
GitHub Actions
Inactive
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #3872 +/- ##
==========================================
- Coverage 75.47% 68.77% -6.70%
==========================================
Files 235 235
Lines 15793 15793
==========================================
- Hits 11919 10861 -1058
- Misses 3133 4261 +1128
+ Partials 741 671 -70 |
laurentsimon
approved these changes
Feb 13, 2024
spencerschrock
commented
Feb 13, 2024
spencerschrock
temporarily deployed
to
gitlab
February 13, 2024 17:27 — with
GitHub Actions
Inactive
spencerschrock
temporarily deployed
to
integration-test
February 13, 2024 17:27 — with
GitHub Actions
Inactive
2 tasks
fhoeborn
pushed a commit
to fhoeborn/scorecard
that referenced
this pull request
Apr 1, 2024
* check logger counts for SAST tests previously, we only checked the result score. test failures with this method dont produce as actionable feedback. Signed-off-by: Spencer Schrock <[email protected]> * clarify test names and score constants used Signed-off-by: Spencer Schrock <[email protected]> --------- Signed-off-by: Spencer Schrock <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
test cleanup
What is the current behavior?
we only checked the result score, which produces test failures without clear actionable feedback.
I discovered this during another refactor and it was hard to figure out what the issue was.
What is the new behavior (if this is a feature change)?**
We use our test helper:
ValidateTestReturn
, which provides much more actionable feedback when tests fail:Which issue(s) this PR fixes
NONE
Special notes for your reviewer
The warn/info/debug counts were just taken as-is from the current state of
main
branch.Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)