yegor256/micromap

we don't use fuzz testing

Open

#299 opened on May 11, 2025

View on GitHub
 (0 comments) (1 reaction) (1 assignee)Rust (17 forks)github user discovery
bughelp wanted

Repository metrics

Stars
 (206 stars)
PR merge metrics
 (Avg merge 8d 16h) (10 merged PRs in 30d)

Description

We should use fuzz testing if we want the highest possible quality for our tests.

Maybe this one may be helpful: https://github.com/rust-fuzz/cargo-fuzz

Contributor guide

Research direction
Set up cargo fuzz and create fuzz targets to test various map operations (insert, get, remove) for edge cases and potential panics.
Tech stack
rust
Domain
backend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65