ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
CI: End-to-end tests for async
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem?
We currently lack end-to-end CI tests for the async pipeline, which leads to unnoticed regressions impacting customers. Without monitoring and alerting, issues may persist before they are detected.
Describe the solution you'd like
- Add end-to-end CI tests for the async pipeline using a dedicated test account.
- Run tests every 5 minutes on /llm/call, /llm/chain, and collection/document flows.
- Verify job completion within SLA, validate responses, and ensure correct callback delivery.
- Implement alerts for failures or latency breaches.
- Track success rate, latency, and callback delivery in dashboards.
- Run these tests on every PR and block merges if they fail.
Original issue
Add end-to-end CI tests for the full async pipeline by using a dedicated production test account. Every 5 minutes, run small test jobs against /llm/call, /llm/chain, and collection/document flows, verify jobs complete within SLA, responses are valid, and callbacks arrive correctly. Alert on failures or latency breaches, and track success rate, latency, and callback delivery in dashboards so pipeline issues are caught within minutes, before customers notice.Run these tests on every PR and block merges if they fail, so async regressions never reach main unnoticed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the async pipeline behind /llm/call, /llm/chain, and collection/document flows, then review the existing CI configuration and test entry points. Done means scheduled and per-PR end-to-end checks verify SLA completion, responses, and callbacks, with failure or latency alerts and success-rate, latency, and callback-delivery dashboards.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, observability, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100