Extending CI with address sanitizers and fuzzy testing

Open
  • Is something wrong?
#88 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
cpp
Domain
build-system, ci-cd, security, testing-qa

Research direction

Start by locating the repository's CI/build configuration and test entry points; the issue names no specific files or tests. Define the sanitizer and fuzzing targets, their CI execution, and measurable passing criteria before implementing; done means both run successfully in CI and support the OpenSSF Best Practices Badge requirement.

Written by the indexing model from the issue text.

Description

enhancement

We would like to improve the quality of our tests by enabling address sanitization instrumentation to the builds. Alongside this, we also would like to add fuzzy testing to OpenQMC. Both of these additions would help maintain the project, catch potential bugs earlier, and improve security.

This is also a requirement For OpenQMC to reach 100% on its OpenSSF Best Practices Badge. Something that is an active goal for the project.

Dominant language
C++
Stars
106
Forks
7
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AcademySoftwareFoundation/openqmc

All issues in AcademySoftwareFoundation/openqmc

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.