Skip to content

Commit 8788fc2

Browse files
authored
fix(e2e): correct stale fuzzing info count for scorecard-webapp (#5253)
The e2e Fuzzing check test against ossf/scorecard-webapp expected 3 info messages (1 for OSS-Fuzz integration, 2 for native Go fuzz functions). The native fuzz functions (FuzzVerifyWorkflow, FuzzExtractCertInfo) have since moved to ossf/scorecard-infra, so the check now correctly reports only the OSS-Fuzz integration signal. Note: OSS-Fuzz's status.json does not yet track ossf/scorecard-infra as a project (see google/oss-fuzz#16140, unmerged), so this expected value may need to change again once that lands. Assisted-by: LLM Signed-off-by: Stephen Augustus <[email protected]>
1 parent f92023a commit 8788fc2

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎e2e/fuzzing_test.go‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ var _ = Describe("E2E TEST:"+checks.CheckFuzzing, func() {
5353
Error: nil,
5454
Score: checker.MaxResultScore,
5555
NumberOfWarn: 0,
56-
NumberOfInfo: 3, // 1 for OSSFuzz, 2 for go native fuzzing
56+
NumberOfInfo: 1, // 1 for OSSFuzz; native fuzz funcs moved to ossf/scorecard-infra
5757
NumberOfDebug: 0,
5858
}
5959
result := checks.Fuzzing(&req)

0 commit comments

Comments
 (0)