AI agent testing guide

[codebestia]

Write apps/ai_agent/docs/testing.md: the pytest setup, the fixtures in tests/conftest.py (client, mock_openai, mock_weaviate, the autouse API-key fixture), and how to add a test for a new endpoint without calling a real model or vector store.

Acceptance criteria:

• Documents each fixture, what it patches and the default it returns
• Gives a worked example of adding an endpoint test using the existing fixtures
• Documents the coverage configuration and how to read the report
• Notes the known gap that /index/message has no dedicated test module, so a contributor can pick it up

[Senatormike001]

@Senatormike001 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

‎I’d be happy to take ownership of this issue to deliver a quality pull request once completed.
‎I’ve thoroughly reviewed the requirements and can work on fixing the issue while ensuring the implementation meets the acceptance criteria.
‎

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Senatormike001 to this issue.

[Fhatu12]

@Fhatu12 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Please assign me to this issue. I’ve reviewed the current AI-agent testing setup and confirmed that the fixtures and coverage configuration described here are all present on main.

I’ll add apps/ai_agent/docs/testing.md and document the existing client, mock_openai, mock_weaviate, and autouse API-key fixtures, including what each fixture patches and how it behaves in the current test suite.

I’ll include a worked endpoint-test example based on the repository’s existing pytest patterns, showing how to use TestClient together with the mocked OpenAI and Weaviate clients so contributors do not accidentally call a real model or vector store.

I’ll also document the current pytest/pytest-cov configuration, explain the term-missing coverage output and CI coverage workflow, and explicitly record the current /index/message dedicated-test gap without expanding this documentation task into implementing that separate test coverage.

I’ll keep the change documentation-only, validate every command and example against the current AI-agent test setup, and run the relevant documentation/AI-agent checks before submitting.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Fhatu12 to this issue.

[0xDeon]

@0xDeon has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello team.

I’m Deon (0xDeon), a software engineer with a strong background in building scalable systems and contributing to open-source projects. I’ve taken some time to go through the repository and understand the current implementation, and I’m clear on the issue, its context, and the expected outcome.

I’d love to work on this and take ownership of the fix. I’m confident I can cleanly resolve it while keeping everything aligned with the existing codebase and ensuring all criteria are met. Would appreciate being assigned to this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @0xDeon to this issue.

[drips-wave]

Congratulations, @0xDeon! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @0xDeon: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊