Repository navigation
Conversation
Every wasm-bindgen wrapper is cfg(not(tarpaulin_include)), so the Rust 100% never measures the JS/WASM boundary. The existing identity and validation oracles already drive it but nothing ran them against WASM. test:wasm-abi runs both against the built WASM package next to the host native addon (public corpus byte-identical across engines, every invalid argument shape rejected with the same TypeError and no state change), then joins the generated index.d.ts with what the runs reached: every export and Output member must be called and every argument position must have a rejection case, except documented exemptions. The table goes to the CI step summary. The publish check job runs it after the tests. Refs #683 (INF-04) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
This was referenced Nov 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
INF-04: Rust 100% 커버리지가 실제 JS/WASM ABI를 측정하지 않는 문제를 다룹니다.
wasm-bindgen 래퍼(
importSheet,codeExtract,setModuleResolver등)는 모두cfg(not(tarpaulin_include))라서 tarpaulin이 경계를 세지 않습니다. 저장소에는 이미 두 엔진을 함께 검증하는 오라클이 있었지만(e2e/binding/identity.mjs,e2e/binding/validation.mjs) CI에서 WASM 대상으로 돌지 않았습니다(native-coverage는 네이티브만 실행).e2e/binding/wasm-abi/run.mjs(bun run test:wasm-abi)identity.mjs: 공개 코퍼스 25개 시나리오를 WASM, 네이티브 각각 3회 실행하고 기록을 바이트 단위로 비교합니다(ABI 이름, arity 검사 포함).validation.mjs: 45개 인자 위치 × 267개 잘못된 입력을 두 엔진에서 실행하고, 같은TypeError메시지와 상태 불변을 확인합니다.pkg/index.d.ts와 실제로 도달한 호출을 합쳐 ABI 커버리지 리포트를 Rust 커버리지와 따로 만듭니다. 결과는 step summary와 evidence 디렉터리의abi-coverage.json에 남습니다.e2e/binding/wasm-abi/coverage.mjs: 리포트 로직입니다. 다음 경우 실패합니다.Output멤버(getter,free,Symbol.dispose)가 한 번도 호출되지 않은 경우.d.ts에 선언된 인자 위치에 rejection 케이스가 없는 경우hasDevupUI.import_aliases하나입니다.argument-validation.cjs가 검증하지 않는 위치라 사유와 함께 명시했습니다.publish검사 job에서 테스트 후WASM ABI coverage단계로 실행합니다(로컬 기준 약 1.5분). release/publish 동작은 변경하지 않았습니다.packages/*변경이 없어서 changepack은 추가하지 않았습니다.Test plan
node --test e2e/binding/wasm-abi/coverage.test.mjs(7 pass)bun run test:wasm-abi: 로컬 WASM, 네이티브 빌드로 identity PASS, validation 534/534, ABI 리포트 okbunx prettier --single-quote --no-semi --check e2e/binding/wasm-abipublishjob의WASM ABI coverage단계와 step summary 표 확인Refs #683
🤖 Generated with Claude Code