ordinals/ord

Check fuzz testing on CI

Open

#1,285 opened on Jan 18, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (1,479 forks)github user discovery
good first issueprocess

Repository metrics

Stars
 (3,955 stars)
PR merge metrics
 (Avg merge 15d 21h) (5 merged PRs in 30d)

Description

We don't need to actually fuzz on CI, but we should check that the fuzz target builds correctly.

Contributor guide

Research direction
Add a CI step to compile the fuzz target. For example, run 'cargo build manifest path fuzz/Cargo.toml' to verify the fuzz target builds correctly.
Tech stack
rust
Domain
testingci cd
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustCargoFuzz testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50