Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

chatcops test: --url to test a deployed server

Abierto
#419 3 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@srujankaleru2007 ya está trabajando en esto.

Desde el 28/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

enhancement hacktoberfest testing

chatcops test runs the bot in process from the config. --url https://example.com/chat runs the same eval files against a deployed server instead, over the wire protocol, as a smoke test after a deploy.

What to add

  • In packages/cli/src/test/run.ts, runOnce (line 86) sends each turn with sendTurn (line 135), which calls the handler in process. Add a second way to send a turn: POST the same body to the URL with format: 'v1' (see website/src/content/docs/server/protocol.mdx for the request and the stream), parse the stream into the same TurnResult, and keep the conversationId across turns.
  • With --url, the server config isn't needed. A test with mocks can't run that way, so fail it with a reason that says so instead of skipping it quietly.
  • --header "Authorization: Bearer ..." (repeatable) for servers that need it. Never print header values.
  • The server's rate limit will apply, so mention --concurrency 1 in the docs. Recording with --record works the same way, since replays happen at the fetch level (packages/cli/src/test/cassette.ts).

Acceptance criteria

  • Tests against a real server started in the test with createChatHandler and node:http (see packages/server/tests for examples), including multi-turn, an error part and a refused request
  • Documented in website/src/content/docs/core/testing.mdx, with a changeset for @chatcops/cli (minor)
  • pnpm test:coverage and pnpm lint pass
Lenguaje dominante
TypeScript
Estrellas
13
Forks
7
Merge medio
3 h 30 min
PR fusionados (30 d)
258

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de codercops/chatcops

Todos los issues de codercops/chatcops

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.