Project: Windows and fuzz runs in continuous integration

Open
#249 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp, github-actions
Domain
ci-cd, testing-qa

Research direction

Start from the existing .github/workflows CI configuration and the Linux build/test steps, then compare the release workflow that already builds Windows. Locate how the fuzz targets are defined and invoked in the build so the same commands can run in a short CI job. Done means pushes and pull requests run Windows build/tests and each fuzz target briefly, with crashing inputs uploaded as build artifacts.

Written by the indexing model from the issue text.

Description

area:project enhancement

CI builds and tests only on Linux. Windows builds only when a release is tagged, so a change that breaks Windows is found late. The fuzz targets never run in CI.

  • Build and run the tests on Windows on every push and pull request
  • Run each fuzz target for a short time on every change
  • Upload any crashing inputs as build artifacts

Split from #23

Dominant language
C++
Stars
4
Forks
1
Avg merge
2h 22m
Merged PRs (30d)
156

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 tomast1337/RCT3PlusPlus

All issues in tomast1337/RCT3PlusPlus

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.