Skip to content

test: cover export fallback behavior#533

Open
seonghobae wants to merge 5 commits into
developfrom
codex/clean-export-utility-coverage
Open

test: cover export fallback behavior#533
seonghobae wants to merge 5 commits into
developfrom
codex/clean-export-utility-coverage

Conversation

@seonghobae

@seonghobae seonghobae commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • adds focused desktop export tests for missing exportSummary fallback behavior
  • verifies metadata handoff defaults emit an explicit empty sourceAssets array and do not include sourcePath when no local source bootstrap is supplied
  • replaces the useful export-test slice of 🧪 [Testing] Increase coverage for export utilities #432 without carrying unrelated YouTube downloader changes

Verification

  • npm ci
  • npm --workspace apps/desktop exec vitest run src/lib/export.test.ts --coverage.enabled=false
  • npm --workspace apps/desktop run typecheck
  • npm --workspace apps/desktop run lint
  • npm --workspace apps/desktop run test
  • npm --workspace apps/desktop run build
  • git diff --check

Supersedes #432.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot couldn't run its full agentic review because no GitHub Actions runner was available. Make sure your repository has a runner available to run Copilot's review, or add a copilot-setup-steps.yml file specifying one with the runs-on attribute. See the docs for more details.

Adds targeted Vitest coverage around desktop export fallback behavior when exportSummary is missing, and tightens assertions for metadata-only handoff output to avoid leaking source-path related data.

Changes:

  • Added a test to validate chart summary JSON generation when exportSummary is absent.
  • Strengthened the “metadata-only local handoff” test with assertions around sourceAssets and sourcePath.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread apps/desktop/src/lib/export.test.ts Outdated
Comment thread apps/desktop/src/lib/export.test.ts
@seonghobae

Copy link
Copy Markdown
Collaborator Author

Addressed the export fallback review feedback in 9e4bd26.

Changes:

  • construct the missing-exportSummary fixture by deleting the property so the absent-field path is actually exercised
  • clarified the metadata handoff default contract: sourceAssets is an explicit empty array when no source bootstrap is present, and sourcePath remains omitted
  • updated the PR description to match that schema contract

Verification:

  • npx vitest run src/lib/export.test.ts - 18 passed
  • npm run lint --workspace @bandscope/desktop - passed
  • npm run typecheck --workspace @bandscope/desktop - passed
  • npm run test --workspace @bandscope/desktop - 122 passed, coverage 100%
  • python3 scripts/checks/security_gates.py - passed
  • python3 scripts/checks/verify_supply_chain.py - passed
  • python3 scripts/checks/verify_security_notes.py - passed
  • git diff --check - passed

Note: the previous security-audit failure is the shared Rust quick-xml RustSec blocker affecting the PR queue, not this desktop export test change. I am handling that in the P0 security track.

@seonghobae seonghobae enabled auto-merge (squash) July 2, 2026 10:42
@opencode-agent

opencode-agent Bot commented Jul 2, 2026

Copy link
Copy Markdown

OpenCode Review Overview

  • Head SHA: c3f0b78cbd336d20e45b73906e7623243890e6bf
  • Workflow run: 28623343145
  • Workflow attempt: 1
  • Gate result: APPROVE (approval step)

Pull request overview

OpenCode reviewed the current-head bounded evidence and found no blocking issues.

Findings

No blocking findings.

Summary

Approval sufficiency: bounded evidence supplied affirmative approval evidence for changed files, coverage/docstring posture, risk surfaces, and current-head verification; approval is not based merely on the absence of known blockers.
Verification posture: CodeGraph evidence was initialized and bounded current-head evidence reviewed for changed-file evidence including apps/desktop/src/lib/export.test.ts.
Linter/static: workflow/static review evidence is bounded by the current-head GitHub Checks gate and changed-file evidence.
TDD/regression: coverage execution evidence and focused changed hunks were reviewed from bounded-review-evidence.md.
Coverage: coverage execution evidence reports supported repository test suites passed.
Docstring coverage: coverage execution evidence reports configured repository docstring gates passed or docstring coverage was advisory.
DAG: CodeGraph/source-backed behavior map connects apps/desktop/src/lib/export.test.ts to the affected review, runtime, or workflow path and required checks.
PoC/execution: coverage-evidence job executed on the current head and reported PASS.
DDD/domain: workflow and repository-governance invariants were reviewed against changed files in bounded evidence.
CDD/context: CodeGraph evidence, changed-file history, and focused hunks were reviewed from bounded-review-evidence.md.
Similar issues: changed-file history evidence was reviewed for comparable local precedents.
Claim/concept check: bounded evidence, repository source, current-head workflow evidence, and, where numeric, scientific, statistical, or literature-backed claims are affected, original-paper/formula evidence and parameter-recovery expectations were used for claims.
Standards search: standards and external-source checks are delegated to configured OpenCode web_search/Context7/DeepWiki sources when applicable; no evidence-backed standards blocker is present in bounded evidence.
Compatibility/convention: changed workflow/script conventions, object naming, and reserved-word safety for schema/API/config/code surfaces were checked in bounded evidence.
Breaking-change/backcompat: deployment evidence and changed-file history were checked for backward-compatibility risk.
Performance: changed surfaces were checked for performance risk in bounded evidence.
Developer experience: changed automation, review, test, setup, and maintenance surfaces were checked for helpful or obstructive DX impact in bounded evidence.
User experience: connected user, operator, API, CLI, documentation, review-comment, status-check, rendering, and workflow-reader behavior was checked for contradictions against code, docs, and tests in bounded evidence.
Visual/DOM: Playwright visual, DOM locator, ARIA snapshot, console, and responsive evidence were checked when a web UI surface was present; for non-web surfaces, API/CLI/log/docs/workflow interaction evidence was reviewed instead.
Accessibility/i18n: accessibility, localization, and human-readable text surfaces were checked where UI, CLI, API message, docs, logs, or review text changed.
Supply-chain/license: dependency, package, model, container, and external-tool changes were checked in bounded evidence.
Packaging: package, build, test, lint, and security contracts were checked in bounded evidence.
Security/privacy: workflow-token, review-gate, and repository-automation security/privacy boundaries were checked in bounded evidence.

  • Result: APPROVE
  • Reason: Test coverage improvement with passing checks
  • Head SHA: c3f0b78cbd336d20e45b73906e7623243890e6bf
  • Workflow run: 28623343145
  • Workflow attempt: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file: export.test.ts"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file: export.test.ts"]
  R1 --> V1["required checks"]
Loading

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode reviewed the current-head bounded evidence and found no blocking issues.

Findings

No blocking findings.

Summary

Approval sufficiency: bounded evidence supplied affirmative approval evidence for changed files, coverage/docstring posture, risk surfaces, and current-head verification; approval is not based merely on the absence of known blockers.
Verification posture: CodeGraph evidence was initialized and bounded current-head evidence reviewed for changed-file evidence including apps/desktop/src/lib/export.test.ts.
Linter/static: workflow/static review evidence is bounded by the current-head GitHub Checks gate and changed-file evidence.
TDD/regression: coverage execution evidence and focused changed hunks were reviewed from bounded-review-evidence.md.
Coverage: coverage execution evidence reports supported repository test suites passed.
Docstring coverage: coverage execution evidence reports configured repository docstring gates passed or docstring coverage was advisory.
DAG: CodeGraph/source-backed behavior map connects apps/desktop/src/lib/export.test.ts to the affected review, runtime, or workflow path and required checks.
PoC/execution: coverage-evidence job executed on the current head and reported PASS.
DDD/domain: workflow and repository-governance invariants were reviewed against changed files in bounded evidence.
CDD/context: CodeGraph evidence, changed-file history, and focused hunks were reviewed from bounded-review-evidence.md.
Similar issues: changed-file history evidence was reviewed for comparable local precedents.
Claim/concept check: bounded evidence, repository source, current-head workflow evidence, and, where numeric, scientific, statistical, or literature-backed claims are affected, original-paper/formula evidence and parameter-recovery expectations were used for claims.
Standards search: standards and external-source checks are delegated to configured OpenCode web_search/Context7/DeepWiki sources when applicable; no evidence-backed standards blocker is present in bounded evidence.
Compatibility/convention: changed workflow/script conventions, object naming, and reserved-word safety for schema/API/config/code surfaces were checked in bounded evidence.
Breaking-change/backcompat: deployment evidence and changed-file history were checked for backward-compatibility risk.
Performance: changed surfaces were checked for performance risk in bounded evidence.
Developer experience: changed automation, review, test, setup, and maintenance surfaces were checked for helpful or obstructive DX impact in bounded evidence.
User experience: connected user, operator, API, CLI, documentation, review-comment, status-check, rendering, and workflow-reader behavior was checked for contradictions against code, docs, and tests in bounded evidence.
Visual/DOM: Playwright visual, DOM locator, ARIA snapshot, console, and responsive evidence were checked when a web UI surface was present; for non-web surfaces, API/CLI/log/docs/workflow interaction evidence was reviewed instead.
Accessibility/i18n: accessibility, localization, and human-readable text surfaces were checked where UI, CLI, API message, docs, logs, or review text changed.
Supply-chain/license: dependency, package, model, container, and external-tool changes were checked in bounded evidence.
Packaging: package, build, test, lint, and security contracts were checked in bounded evidence.
Security/privacy: workflow-token, review-gate, and repository-automation security/privacy boundaries were checked in bounded evidence.

  • Result: APPROVE
  • Reason: Test coverage improvement with passing checks
  • Head SHA: c3f0b78cbd336d20e45b73906e7623243890e6bf
  • Workflow run: 28623343145
  • Workflow attempt: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file: export.test.ts"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file: export.test.ts"]
  R1 --> V1["required checks"]
Loading

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.

2 participants