Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

remake fuzzing from scratch

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
testing-qa

Research direction

Start by reading the existing fuzzing implementation under fuzz/ and review issue #656 to understand how it was nearly broken. Replace the obscure setup with a new fuzzing approach, likely as a special test; the implementation details and completion criteria are not specified in the issue.

Written by the indexing model from the issue text.

Description

help wanted r-testing

our current fuzzing is obscure and no one really knows how it works

it is under fuzz/

it was back from when the repo didn't even use GitHub actions, it used travis-CI, for perspective

and I almost broke it with #656

simple: take it down and build new fuzzing, probably in the form of some sort of special test

implementation details are left for you to decide

Dominant language
Rust
Stars
1.7k
Forks
218
Avg merge
19h 1m
Merged PRs (30d)
105

Contributor guide

No contributing guide indexed for this repository

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 servo/rust-smallvec

All issues in servo/rust-smallvec

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.