Skip to content

introduce fuzz testing of the library using llvm libfuzzer#150

Open
rdmark wants to merge 1 commit intomainfrom
fuzz-testing
Open

introduce fuzz testing of the library using llvm libfuzzer#150
rdmark wants to merge 1 commit intomainfrom
fuzz-testing

Conversation

@rdmark
Copy link
Collaborator

@rdmark rdmark commented Mar 7, 2026

with clang and llvm's libfuzzer, fuzzed data can be fed into the functions under test to stress test them with random input values

@github-actions
Copy link

github-actions bot commented Mar 7, 2026

File Coverage Lines Branches
All files 69% 74% 63%
bstring/bstraux.c 55% 64% 47%
bstring/bstrlib.c 74% 78% 71%
bstring/buniutil.c 80% 86% 73%
bstring/utf8util.c 60% 71% 50%

Minimum allowed coverage is 50%

Generated by 🐒 cobertura-action against c2bda4b

@rdmark rdmark force-pushed the fuzz-testing branch 8 times, most recently from 1d1bfd1 to 045c13f Compare March 7, 2026 23:01
@rdmark
Copy link
Collaborator Author

rdmark commented Mar 7, 2026

running the fuzzing locally on my Debian Trixie machine led to two bugs being found

will keep this PR as draft until these have been merged

@rdmark rdmark marked this pull request as ready for review March 17, 2026 21:52
@rdmark rdmark requested a review from msteinert as a code owner March 17, 2026 21:52
@rdmark rdmark force-pushed the fuzz-testing branch 2 times, most recently from 5874d46 to 1ec03af Compare March 18, 2026 06:19
with clang and llvm's libfuzzer, fuzzed data can be fed into the functions under test
to stress test them with random input values
@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
1 Security Hotspot

See analysis details on SonarQube Cloud

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.

1 participant