Fuzz testing: analyze existing repository state
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 冷清
- 技术栈
- kotlin
- 领域
- testing-qa
调研方向
Start by searching the repository for randomized or property-based tests and inspecting test and CI configuration, including how JVM, native, and wasmJs tests run. Review the named parsing targets—skainet-io-gguf, skainet-io-safetensors, skainet-io-onnx, skainet-io-iree-params, tokenizer/BPE, skainet-lang, and skainet-compile—for relevant tests and TODOs or bug reports. Done means posting a concise evidence-based inventory and summary that can guide the design work in #981.
由索引模型根据 Issue 内容生成。
描述
Sub-issue of #981 ("Enhance testing by adding fuzzing") — the A: ASSESS phase for that
proposal. Before designing or adopting anything, establish what's actually already here.
Goal
Inventory the repository's current state as it relates to fuzz testing, so #981's design phase
starts from facts rather than assumptions.
Tasks
- Search for any existing property-based / generative tests across the codebase (
kotlin.test
custom generators, hand-rolled randomized tests, anything resembling fuzzing today) —
distinguish these from ordinary parameterized/table tests. - Identify the highest-value fuzz targets: parsers and format readers are the classic fuzzing
sweet spot —skainet-io-gguf(GGUF),skainet-io-safetensors,skainet-io-onnx,
skainet-io-iree-params(irpa), the tokenizer/BPE code, and any binary/text format parsing
inskainet-lang/skainet-compile. - Check current test coverage tooling/config (if any) and whether coverage data is already
collected in CI, to know what a fuzzing effort would be building on top of vs. introducing
from scratch. - Note existing CI structure relevant to adding a new test category (build-logic conventions,
per-module test source sets, howjvmTest/native/wasmJstest execution differs — a fuzzer
is realistically JVM-only to start, given tooling maturity, so this matters for scoping). - Flag any known crash/hang/OOM bug reports or
TODO/FIXMEcomments near parsing code that
a fuzzer would likely have caught, as motivating examples.
Output
A short written summary (as a comment on this issue, or a doc page) other contributors can use
to scope #981's actual implementation plan — not code, just ground truth about what exists today.
Related
- Parent: #981
- Companion sub-issue (ecosystem research, can run in parallel): link added after creation
- 主要语言
- Kotlin
- 星标
- 52
- 派生
- 15
- 平均合并
- 1 天 1 小时
- 30 天内合并 PR
- 41
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
SKaiNET-developers/SKaiNET 的其他 Issue
-
coding good first issue platform size:xs skill:js sub-issue
难度 2/5 1-3 小时 新手友好度 72/100
SKaiNET-developers/SKaiNET#1232 ·
维护者通常 1 天内回复
-
enhancement platform skill:native sub-issue
难度 4/5 3-5 天 新手友好度 52/100
SKaiNET-developers/SKaiNET#1301 ·
维护者通常 1 天内回复
-
compute-backend skill:android tracking
难度 5/5 一周以上 新手友好度 20/100
SKaiNET-developers/SKaiNET#1282 ·
维护者通常 1 天内回复
-
compiler enhancement skill:numerics
难度 5/5 一周以上 新手友好度 35/100
SKaiNET-developers/SKaiNET#1281 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement skill:kotlin-core skill:numerics
难度 5/5 一周以上 新手友好度 25/100
SKaiNET-developers/SKaiNET#1280 · 1 条评论 ·
维护者通常 1 天内回复
查看 SKaiNET-developers/SKaiNET 的全部 Issue
相似的 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
enhancement triaged
难度 1/5 1 小时以内 新手友好度 63/100
维护者通常 1 天内回复
-
bug follow-up
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
bug 🐞 CI/CD ⚒️
难度 2/5 1-3 小时 新手友好度 78/100
valkey-io/valkey-glide#7370 ·
维护者通常 1 天内回复
-
binding:web core docs p3
难度 2/5 1-3 小时 新手友好度 85/100
RunanywhereAI/runanywhere-sdks#1123 ·
维护者通常 1 天内回复