Skip to content

test(devicetree): cover summary counts, node paging, and property selection in devicetree views - #7305

Open
saiyam-jain-dev wants to merge 2 commits into
morluto:mainfrom
saiyam-jain-dev:test/devicetree-view-coverage
Open

saiyam-jain-dev wants to merge 2 commits into
morluto:mainfrom
saiyam-jain-dev:test/devicetree-view-coverage

Conversation

@saiyam-jain-dev

@saiyam-jain-dev saiyam-jain-dev commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Adds comprehensive unit tests in src/domain/analysisView/devicetreeView.test.ts covering Devicetree analysis view projections, including summary count/reference calculations, node paging, property selection by node path, collection validation rules, and error handling for unsupported view kinds and missing node paths.

Problem and expected behavior

While projectDevicetreeView implements summary and paging views for Flattened Devicetree (.dtb) inspection evidence, it previously lacked a dedicated unit test suite covering its projection logic, collection validation rules (e.g. requiring path for properties, rejecting path for reservations/references, and handling nonexistent nodes), and calculated summary counters.

Change and scope

  • Created src/domain/analysisView/devicetreeView.test.ts verifying:
    • Summary view calculation of reservation_count, reference_count, and unresolved_reference_count.
    • Node collection paging with omission of nested properties, calculation of property_count, and assignment of source_index.
    • Node selection by exact path preserving original node index.
    • Property paging for a selected node path.
    • Refusal of property queries without a path or with an absent node path.
    • Reservation and reference collection paging with source_index.
    • Refusal of path on collections that do not support path selection.
    • Rejection of unsupported view kinds 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/devicetreeView.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/devicetreeView.test.ts
  • Base reproduction or other evidence: previously unexercised projection code.
  • 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/devicetreeView.test.ts — passed (9 passed in 35ms)
  • npm run check:fast (turbo run typecheck lint) — passed cleanly (2/2 tasks successful in 50s)

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.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ⚠️ Failed 2026-10-26T22:16:08.497789Z
We couldn’t complete this review. Comment @codex review to try again.
a8e0415 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@saiyam-jain-dev

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Something went wrong. Try again later by commenting “@codex review”.

An unknown error occurred
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@greptile-apps

greptile-apps Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] The test-only PR appears safe to merge.

Summary

Adds tests for Devicetree summary counts, node and property selection, paging, and rejected requests.

  • Devicetree view tests now cover summaries, paging, and path selection.

Reviews (2) · Last reviewed commit: "test(devicetree): cover subsequent page ..." · Reviewed by Greptile

Comment thread src/domain/analysisView/devicetreeView.test.ts
Comment thread src/domain/analysisView/devicetreeView.test.ts Outdated

This branch has not been deployed

No deployments
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