Skip to content

test(web): Perplexity + Exa coverage; strip section-banner comments#1366

Merged
esengine merged 1 commit into
mainfrom
chore/web-search-followups
May 20, 2026
Merged

test(web): Perplexity + Exa coverage; strip section-banner comments#1366
esengine merged 1 commit into
mainfrom
chore/web-search-followups

Conversation

@esengine

Copy link
Copy Markdown
Owner

Summary

Silent follow-ups to #1350:

  • Add 5 unit tests each for Perplexity and Exa in `tests/web-tools.test.ts` (missing-key / 401 / 429 / parse-error / body shape with right auth header) — mirror what tavily already had so a fetch-shape change can't regress these backends silently.
  • Add a `formatSearchResults` case for the new `answer + sources` dual-section branch (was untested when added).
  • Drop the `// ── Perplexity ──` / `// ── Exa ──` / `// ── API-key engines ──` section-banner separators that Feat/web-search perplexity exa #1350 introduced. CLAUDE.md bans them.

No behavior change. `tests/web-tools.test.ts` goes 43 → 54 tests.

Test plan

  • `npx vitest run tests/web-tools.test.ts` — 54/54 green
  • `npm run lint` clean
  • `npm run verify` runs in pre-push hook

…ents

Two follow-ups to #1350:

1. Perplexity / Exa landed without unit tests, while tavily has 5
   covering missing-key / 401 / 429 / parse-error / body shape. Mirror
   that pattern so a fetch-shape change in either backend can't regress
   silently. Also add a formatSearchResults case for the new "answer +
   sources" dual-section branch.

2. Drop the `// ── Perplexity ──` / `// ── Exa ──` / `// ── API-key
   engines ──` section-banner separators — CLAUDE.md bans them; group
   by export instead.
@esengine esengine merged commit eb06c32 into main May 20, 2026
4 checks passed
@esengine esengine deleted the chore/web-search-followups branch May 20, 2026 01:32
ChasLui pushed a commit to ChasLui/DeepSeek-Reasonix that referenced this pull request May 23, 2026
…ents (esengine#1366)

Two follow-ups to esengine#1350:

1. Perplexity / Exa landed without unit tests, while tavily has 5
   covering missing-key / 401 / 429 / parse-error / body shape. Mirror
   that pattern so a fetch-shape change in either backend can't regress
   silently. Also add a formatSearchResults case for the new "answer +
   sources" dual-section branch.

2. Drop the `// ── Perplexity ──` / `// ── Exa ──` / `// ── API-key
   engines ──` section-banner separators — CLAUDE.md bans them; group
   by export instead.

Co-authored-by: reasonix <reasonix@deepseek.com>
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