esperar uip tm

Sintaxis y opciones para `uip tmwait`, que sondea una ejecución de prueba hasta que alcanza un estado terminal e imprime un resumen de una línea.

uip tm wait polls a test execution until it reaches a terminal state (Finished or Cancelled) and then prints a one-line summary. It turns the asynchronous uip tm testsets run into a blocking step in a CI pipeline.

wait is registered as a top-level verb under tm, not as a resource. Invoke it as uip tm wait, not uip tm executions wait.

Sinopsis

uip tm wait --execution-id <uuid> (--project-key <key> | --project-id <id> | --test-set-key <key>)
            [--timeout <seconds>]

Respeta las opciones globales. Consulta la sección Códigos de salida a continuación para ver el comportamiento específico del dominio en el tiempo de espera.

esperar uip tm

Block until the given execution reaches a terminal state, polling Test Manager every 60 seconds.

Argumentos

Nada.

Opciones

• --execution-id <uuid> (obligatorio) : ejecución a esperar. Obtenlo de uip tm testsets run.

• --project-key <key> — owning project key.

• --project-id <id> — owning project ID. Use instead of --project-key.

  Pass --project-id, --project-key, or --test-set-key. When you pass more than one, --project-id is used first, then --project-key, then the project prefix of --test-set-key.

• --test-set-key <key> : clave del conjunto de pruebas (por ejemplo, DEMO:42); la clave del proyecto se deriva del prefijo.

• --timeout <seconds> — maximum time to wait, in seconds. Defaults to 1800 (30 minutes). Pass 0 to wait indefinitely.

Nota:

There is no --poll-interval flag on this command. The poll interval is fixed at 60 seconds.

ADVERTENCIA:

A manual run closed early with executions finish keeps Status: "Running", so wait never sees a terminal state on it. wait blocks until --timeout and then exits 2. Check such a run's ExecutionFinished timestamp with executions get-stats instead.

Ejemplo

# wait up to 15 minutes
uip tm wait \
  --execution-id a1b2c3d4-0000-0000-0000-000000000001 \
  --project-key DEMO \
  --timeout 900

Data shape (terminal state reached before the timeout)

{
  "Code": "WaitComplete",
  "Data": {
    "ExecutionId": "a1b2c3d4-0000-0000-0000-000000000001",
    "Status": "Finished",
    "EndTime": "2025-04-15T10:32:11Z",
    "Duration": "00:02:11"
  }
}

Status is the terminal state Test Manager reports: Finished or Cancelled. Reaching a terminal state is the success signal for wait; the verb exits 0 whether the tests inside the execution passed or failed. To branch on pass or fail, read the report get output after wait returns.

Códigos de salida

wait sigue los códigos de salida estándar para 0, 1 y 3, con una reutilización específica del dominio de 2:

Código de salida	Significado
0	La ejecución alcanzó un estado terminal dentro del tiempo de espera.
1	Polling failed (three consecutive API errors, interrupt, abort), sign-in failed, or no project was given. See the Message field for detail.
2	Timed out. The timeout elapsed before the execution reached a terminal state.
3	Error de validación (valor de marcador incorrecto, falta la opción obligatoria).

Exit code 2 is domain-specific. The shared CLI contract reserves 2 for AuthenticationError, but wait reuses it for timeout so that scripts can distinguish "took too long" from "polling failed" without parsing text. uip tm run uses 4 for its own timeout instead. See Exit-code behavior on executions for the full pattern.

Patrón de script

uip tm wait \
  --execution-id "$id" \
  --project-key DEMO \
  --timeout 1800
case $? in
  0) ;;
  2) echo "timed out" >&2; exit 2 ;;
  *) echo "wait failed" >&2; exit 1 ;;
esac

Relacionado

• conjuntos de pruebas ejecutados : produce el ExecutionId a esperar.
• informe : resumen para leer una vez wait devuelve 0.
• resultado : exportación XML de JUnit.
• reintento de ejecuciones : vuelve a ejecutar los casos fallidos de una ejecución finalizada.
• executions cancel — stop a running automated execution; poll it to Cancelled with wait.
• run — run every test in an uploaded package, wait, and write a report in one command.

Ver también

• Descripción general de Test Manager
• Códigos de salida : contrato compartido.
• Patrones de scripting : el proceso de lanzamiento-espera-verificación.