Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Fuzz testing: research existing KMP/Kotlin ecosystem tooling

Aperta
  • Qualcosa non va?
#983 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Tranquilla
Stack tecnologico
java, kotlin, machine-learning
Ambito
ai, developer-experience, machine-learning, testing, testing-qa, tooling

Direzione di ricerca

This is research for parent #981, not an implementation ticket. Start from the listed candidates (Jazzer, Jazzer.js, kotest property testing, JUnit/kotlin.test generators) and check which run on KMP source sets versus jvmTest only. Note how each reports coverage (JaCoCo-style, Gradle/CI wiring) and how other Kotlin/JVM OSS projects time-box fuzz jobs, persist corpora, and report crashes. Done is a short comparison comment or doc page so #981 can pick tools; do not implement fuzzing here. Companion #982 can run in parallel.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement research sub-issue

Sub-issue of #981 ("Enhance testing by adding fuzzing") — the R: RESEARCH phase for that
proposal. Survey what already exists in the Kotlin/KMP ecosystem before designing anything custom.

Goal

Answer "what can we reuse" before #981 gets to a design/implementation plan.

Tasks

  • Fuzzing engines/harnesses for Kotlin/JVM: Jazzer
    (JVM libFuzzer via coverage-guided bytecode instrumentation, the most mature option),
    Jazzer.js if a JS/Wasm-side target
    ever makes sense, kotlinx property-based testing options
    (kotest property testing),
    and plain JUnit/kotlin.test + custom generators as a baseline comparison.
  • KMP-specific constraints: which of the above actually work across KMP source sets vs.
    JVM-only — most fuzzing engines are JVM-bytecode-based (Jazzer) or Node-based (Jazzer.js),
    so figure out realistic target-set scope (likely jvmTest only, at least initially) rather
    than assuming multiplatform fuzzing is feasible.
  • Coverage measurement: how each candidate reports/measures coverage (Jazzer integrates
    with JaCoCo-style coverage; check what's practical to wire into this repo's existing
    Gradle/CI setup), and whether coverage-guided fuzzing (vs. blind random generation) is
    achievable here.
  • CI integration patterns: how other Kotlin/JVM OSS projects run fuzzing in CI — as a
    time-boxed job (e.g. N minutes/seeds per run, not exhaustive), corpus persistence between
    runs (cached seed corpus so regressions aren't re-discovered from scratch), and how crashes
    get reported/triaged (e.g. auto-filed issues vs. failing the build).
  • Reporting/eval: what output format(s) these tools produce (crash reproducers, minimized
    inputs, coverage deltas) and whether any of it is consumable by this repo's existing docs/
    Antora pipeline or needs a bespoke summary step.
  • OSS-Fuzz feasibility: whether SKaiNET could realistically be onboarded to
    OSS-Fuzz (free continuous fuzzing for open-source
    projects) given it already has Jazzer-based JVM project examples, as a longer-term option
    beyond local/CI-only fuzzing.

Output

A short comparison write-up (as a comment on this issue, or a doc page) — not a recommendation
that's already implemented, just enough for #981 to make an informed tool choice.

Related

  • Parent: #981
  • Companion sub-issue (repo-state analysis, can run in parallel): #982
Lingua principale
Kotlin
Stelle
52
Fork
15
Merge medio
1g 15h
PR unite (30g)
36

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di SKaiNET-developers/SKaiNET

Tutte le issue di SKaiNET-developers/SKaiNET

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.