SASE QA: Flujos Escolares

This skill defines the procedures for testing critical school workflows.

Mandatory Test Scenarios

1. The Docente Lifecycle

• •Actor: User with role DOCENTE.
• •Steps:
  1. •Login successfully.
  2. •Locate a student (either via list or search).
  3. •Create an incidencia of type "ACADEMICA" (e.g., "No entregó tarea").
  4. •Verify the incident appears in the student's history.
  5. •Attemt to Close the case immediately (should be allowed for simple academic issues).
  6. •Verify closure status.

2. Escalation & Direction

• •Actors: DOCENTE, DIRECCION.
• •Steps:
  1. •Docente: Creates a "GRAVE" incident (e.g., "Conducta Agresiva").
  2. •Docente: Tries to close it? (Should be warned or blocked, or it remains open for Orientation).
  3. •Dirección: Logs in.
  4. •Dirección: Sees the alert/notification.
  5. •Dirección: Adds a comment/observation.
  6. •Dirección: Closes the case.
  7. •Verify: Log out Direction, Log in Docente. Docente checks status -> "CERRADO".

3. Citation (Citatorio) Integration

• •Actor: DOCENTE or ORIENTACION.
• •Steps:
  1. •Generate a Citatorio for a parent.
  2. •Check if it generates a printable view or PDF.
  3. •Verify the database records the "Citatorio Created" event in auditoria.

Automation Instructions

• •Use browser_subagent for these flows.
• •Must capture screenshots at:
  • •Form submission success.
  • •Error messages.
  • •Final state verification.
• •Log any failures precisely (e.g., "Button X not clickable", "RLS Error 401").