Tests that use the local task queue are a bit more involved because, unlike datastore and memcache, the task queue API does not expose a facility for examining the state of the service.
The task consumer can be part of your App Engine application (such as a backend) or a system outside of App Engine (using the Task Queue REST API). Push Queue
El consumidor de tareas puede ser parte de tu aplicación de App Engine (como un backend) o de un sistema fuera de App Engine (con la API de REST de la lista de tareas en cola).
App Engine's Task Queue API is designed to provide "at least once" delivery; that is, if a task is successfully added, App Engine will deliver it to a handler at least once.
La API de la lista de tareas en cola de App Engine está diseñada para brindar una entrega de "al menos una vez"; es decir, si una tarea se agrega correctamente, App Engine la entregará al controlador al menos una vez.
Examples are used only to help you translate the word or expression searched in various contexts. They are not selected or validated by us and can contain inappropriate terms or ideas. Please report examples to be edited or not to be displayed. Potentially sensitive, inappropriate or colloquial translations are usually marked in red or in orange.