ag-testar-codigo

ag-testar-codigo — Testar Codigo

Spawn the ag-testar-codigo agent to create and run unit/integration tests.

Invocation

Use the Agent tool with:

• subagent_type: ag-testar-codigo
• mode: bypassPermissions
• run_in_background: true
• prompt: Compose from template below + $ARGUMENTS

Prompt Template

Projeto: [CWD or user-provided path]
Scope: [modulo especifico, arquivo, ou "full" para suite completa]
Framework: [vitest, jest, pytest, ou "auto-detect"]
Modo: [--from-spec (Red/TDD) | pos-implementacao (Green) | default]


Criar e executar testes. Para suite completa, usar Agent Teams (unit + integration + e2e em paralelo).
Registrar falhas em errors-log.md. Seguir anti-teatralidade: cada expect() DEVE poder falhar.

Important

• ALWAYS spawn as Agent subagent — do NOT execute inline
• After spawning, confirm to the user
• Supports parallel test execution via Agent Teams for full suites
• Follows anti-theatricality rules: no .catch(() => false), no || true, no always-true expects

Tipos de Teste Esperados

NAO faz E2E (browser, UI) — isso e do ag-testar-e2e.

Template por Funcao (minimo)

describe('NomeDaFuncao', () => {
  test('happy path — valor hard-coded da spec', () => {
    expect(fn(validInput)).toBe(expectedOutput); // hard-coded, NUNCA calculado
  });
  test('error path — input invalido retorna erro', () => {
    expect(() => fn(null)).toThrow('Expected error message');
  });
  test('edge case — vazio', () => {
    expect(fn('')).toBe(defaultValue);
  });
  test('edge case — limite/negativo', () => {
    expect(fn(-1)).toBe(boundaryResult);
  });
  // Se app tem roles:
  test('access control — role sem permissao', () => {
    expect(fn(viewerContext)).rejects.toThrow('Forbidden');
  });
});