Skip to content

Add fuzz test for backup cron schedule parsing - #23

Merged
KeiaiLab-PHIL merged 1 commit into
mainfrom
test/fuzz-nextrun
Oct 6, 2026
Merged

KeiaiLab-PHIL merged 1 commit into
mainfrom
test/fuzz-nextrun

Conversation

@KeiaiLab-PHIL

Copy link
Copy Markdown
Contributor

Scorecard FuzzingID flags the repo for having no fuzz targets.
nextRun parses user-supplied spec.schedule, so it is the input
surface most worth fuzzing.

The target asserts no panic, deterministic re-parse, and that an
accepted schedule fires strictly after the reference time on a
minute boundary (zero time allowed for never-firing dates).

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Signed-off-by: phil phil@keiailab.com

🤖 Generated with Claude Code

Scorecard FuzzingID flags the repo for having no fuzz targets.
nextRun parses user-supplied spec.schedule, so it is the input
surface most worth fuzzing.

The target asserts no panic, deterministic re-parse, and that an
accepted schedule fires strictly after the reference time on a
minute boundary (zero time allowed for never-firing dates).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: phil <phil@keiailab.com>
@KeiaiLab-PHIL
KeiaiLab-PHIL enabled auto-merge (squash) October 6, 2026 02:46
@KeiaiLab-PHIL
KeiaiLab-PHIL merged commit 4fb33d1 into main Oct 6, 2026
16 checks passed
@KeiaiLab-PHIL
KeiaiLab-PHIL deleted the test/fuzz-nextrun branch October 6, 2026 02:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant