Add prompt fixtures and stream helpers for tests

[utmishra]

Summary

• add prompt fixtures and streaming utilities for shared test data
• serve deterministic stream in /api/chat when TEST_ROUTES is set
• verify reasoning and tool calls in route and UI tests

Testing

• pnpm test:routes
• pnpm test:e2e (fails: Executable doesn't exist at ... please run playwright install)

---

https://chatgpt.com/codex/tasks/task_e_68a065926fb083209ad6fa89212fd6ae

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull Request Overview

This PR adds test infrastructure for chat functionality by introducing prompt fixtures and streaming utilities for deterministic testing. It replaces OpenAI API-dependent tests with deterministic test data and adds comprehensive verification of reasoning and tool calls.

• Introduces reusable streaming utilities and prompt fixtures for consistent test data
• Updates route tests to verify structured assistant responses including reasoning and tool calls
• Adds end-to-end tests for UI interactions with assistant messages and reasoning details

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
web/tests/routes/chat.spec.ts	Replaces OpenAI-dependent test with deterministic stream parsing and verification
web/tests/prompts/utils.ts	Adds utilities for building and parsing streaming response data
web/tests/prompts/simple.ts	Defines test fixtures for simple chat interactions with reasoning and tool calls
web/tests/e2e/chat.spec.ts	Adds UI tests for assistant messages, reasoning details, and tool output
web/src/app/api/chat/route.ts	Updates test route to use new streaming fixtures instead of generic prompt
web/playwright.config.ts	Configures test environment variables for deterministic behavior

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Using 'any' type defeats the purpose of TypeScript's type safety. Consider using the StreamChunk type or creating a more specific type for chunk objects.

Suggested change

	(c: any) =>
	.filter((c: StreamChunk) => c.type === 'text')
	.map((c: StreamChunk) => c.text)
	.join('');
	expect(text).toBe(simpleAnswerText);
	expect(
	chunks.some(
	(c: StreamChunk) => c.type === 'reasoning' && c.text === simpleReasoning,
	),
	).toBeTruthy();
	expect(
	chunks.some(
	(c: StreamChunk) =>

[Copilot]

Using 'any' type defeats the purpose of TypeScript's type safety. Consider using the StreamChunk type or creating a more specific type for chunk objects.

Suggested change

	(c: any) =>
	.filter((c: StreamChunk) => c.type === 'text')
	.map((c: StreamChunk) => c.text)
	.join('');
	expect(text).toBe(simpleAnswerText);
	expect(
	chunks.some(
	(c: StreamChunk) => c.type === 'reasoning' && c.text === simpleReasoning,
	),
	).toBeTruthy();
	expect(
	chunks.some(
	(c: StreamChunk) =>

[Copilot]

Using 'any' type defeats the purpose of TypeScript's type safety. Consider using the StreamChunk type or creating a more specific type for chunk objects.

Suggested change

	(c: any) =>
	.filter((c: StreamChunk) => c.type === 'text')
	.map((c: StreamChunk) => c.text)
	.join('');
	expect(text).toBe(simpleAnswerText);
	expect(
	chunks.some(
	(c: StreamChunk) => c.type === 'reasoning' && c.text === simpleReasoning,
	),
	).toBeTruthy();
	expect(
	chunks.some(
	(c: StreamChunk) =>

[Copilot]

Using 'any' type defeats the purpose of TypeScript's type safety. Consider using the StreamChunk type or creating a more specific type for chunk objects.

Suggested change

	(c: any) =>
	.filter((c: StreamChunk) => c.type === 'text')
	.map((c: StreamChunk) => c.text)
	.join('');
	expect(text).toBe(simpleAnswerText);
	expect(
	chunks.some(
	(c: StreamChunk) => c.type === 'reasoning' && c.text === simpleReasoning,
	),
	).toBeTruthy();
	expect(
	chunks.some(
	(c: StreamChunk) =>

[Copilot]

The StreamChunk type is too generic. Consider defining a more specific union type based on the actual chunk structures (e.g., TextChunk | ReasoningChunk | ToolChunk) to improve type safety and developer experience.

Suggested change

	export type StreamChunk = Record<string, any>
	export type TextChunk = { type: 'text'; text: string }
	export type ReasoningChunk = { type: 'reasoning'; reasoning: string }
	export type ToolChunk = { type: 'tool'; tool: string; args?: Record<string, any> }
	export type StreamChunk = TextChunk | ReasoningChunk | ToolChunk