[PR #7100] test(rust): cover package filters, edge selectors, and null metadata in Rust views #7642

Open
opened 2026-11-03 13:39:19 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7100
Author: @saiyam-jain-dev
Created: 10/25/2026
Status: 🔄 Open

Base: main ← Head: test/rust-binary-view-coverage


📝 Commits (2)

  • 371a1b5 test(rust): cover package filters, edge selectors, and null metadata in Rust views
  • 3bf2421 test(rust): retrigger ci

📊 Changes

1 file changed (+165 additions, -0 deletions)

View changed files

📝 src/domain/analysisView/rustBinaryView.test.ts (+165 -0)

📄 Description

Summary

Adds unit test coverage in src/domain/analysisView/rustBinaryView.test.ts for package filtering (names, versions, indices), dependency edge selection (from_indices, to_indices), null auditable_metadata handling with compiler commit projections, and invalid view kind rejections in Rust analysis views.

Problem and expected behavior

While projectRustBinaryView supports filtering packages by names, versions, and indices, projecting requested dependencies collections, filtering dependency edges by from_indices and to_indices, projecting binaries without cargo-auditable metadata (auditable_metadata: null), and rejecting unsupported view kinds with analysisViewInputError, these code paths lacked unit test coverage in rustBinaryView.test.ts.

Change and scope

  • Added tests in src/domain/analysisView/rustBinaryView.test.ts verifying:
    • Package filtering by names, versions, and indices, including requested dependencies.
    • Dependency edge filtering by from_indices, to_indices, and fields.
    • Null auditable_metadata summary handling, compiler rustc_commit hashes count projection, and empty package collections.
    • Rejection of unsupported view kinds (e.g. cve) with AnalysisInputError.

Contribution scope fit: test-only coverage improvement within existing boundaries (not applicable).

Contract and boundary impact

  • Semantic owner and earliest changed stage: src/domain/analysisView/rustBinaryView.test.ts.
  • Contribution scope fit and linked maintainer decision: not applicable.
  • CLI and MCP/tool-catalog contract: none.
  • Provider, bridge, target-format, or platform compatibility: platform-independent.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): none.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none.

Expected effects:

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests added or updated: src/domain/analysisView/rustBinaryView.test.ts
  • Base reproduction or other evidence: previously uncovered projection and filtering branches.
  • User-visible CLI/MCP output: none.
  • Remaining proof gaps: none.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npx vitest run src/domain/analysisView/rustBinaryView.test.ts — passed (10 passed in 40ms)
  • npm run check:fast (turbo run typecheck lint) — passed cleanly (2/2 tasks successful in 1m26s)

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: none.

Author readiness

Human owner: @saiyam-jain-dev

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/7100 **Author:** [@saiyam-jain-dev](https://github.com/saiyam-jain-dev) **Created:** 10/25/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `test/rust-binary-view-coverage` --- ### 📝 Commits (2) - [`371a1b5`](https://github.com/morluto/rea/commit/371a1b5234f876add76e0b3d6518b7e8318dc190) test(rust): cover package filters, edge selectors, and null metadata in Rust views - [`3bf2421`](https://github.com/morluto/rea/commit/3bf2421ebae35aa02ef5de4b5810f7b078d86cfa) test(rust): retrigger ci ### 📊 Changes **1 file changed** (+165 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/analysisView/rustBinaryView.test.ts` (+165 -0) </details> ### 📄 Description ## Summary Adds unit test coverage in `src/domain/analysisView/rustBinaryView.test.ts` for package filtering (`names`, `versions`, `indices`), dependency edge selection (`from_indices`, `to_indices`), null `auditable_metadata` handling with compiler commit projections, and invalid view kind rejections in Rust analysis views. ## Problem and expected behavior While `projectRustBinaryView` supports filtering packages by `names`, `versions`, and `indices`, projecting requested `dependencies` collections, filtering dependency edges by `from_indices` and `to_indices`, projecting binaries without cargo-auditable metadata (`auditable_metadata: null`), and rejecting unsupported view kinds with `analysisViewInputError`, these code paths lacked unit test coverage in `rustBinaryView.test.ts`. ## Change and scope - Added tests in `src/domain/analysisView/rustBinaryView.test.ts` verifying: - Package filtering by `names`, `versions`, and `indices`, including requested `dependencies`. - Dependency edge filtering by `from_indices`, `to_indices`, and `fields`. - Null `auditable_metadata` summary handling, compiler `rustc_commit` hashes count projection, and empty package collections. - Rejection of unsupported view kinds (e.g. `cve`) with `AnalysisInputError`. Contribution scope fit: test-only coverage improvement within existing boundaries (not applicable). ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/domain/analysisView/rustBinaryView.test.ts`. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: platform-independent. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): none. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. Expected effects: - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `src/domain/analysisView/rustBinaryView.test.ts` - Base reproduction or other evidence: previously uncovered projection and filtering branches. - User-visible CLI/MCP output: none. - Remaining proof gaps: none. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npx vitest run src/domain/analysisView/rustBinaryView.test.ts` — passed (10 passed in 40ms) - `npm run check:fast` (`turbo run typecheck lint`) — passed cleanly (2/2 tasks successful in 1m26s) ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none. ## Author readiness Human owner: @saiyam-jain-dev - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7642
No description provided.