Add a deterministic Task Processing test provider for LibreSign AI flows
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start by reading the AI foundation capability contract referenced in the issue and identify the task types currently consumed by LibreSign; no specific files or tests are named here. Then inspect how the app integrates with Nextcloud Task Processing and how existing tests provide service doubles. Done means a production-separated, network-free deterministic provider with selectable fixtures and focused tests for the supported success and failure cases.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Goal
Provide a fast, deterministic Task Processing provider/test double that lets LibreSign exercise AI-assisted flows in CI without paid APIs, external network access or probabilistic output.
This issue is part of the AI foundation epic and must follow the capability contract defined by the foundation work.
Why
AI-assisted features need normal regression coverage. Unit mocks alone are not enough to prove that LibreSign integrates correctly with the Nextcloud Task Processing path, while real LLM calls are too slow, costly and nondeterministic for ordinary pull-request CI.
The test provider should make AI behavior as testable as other LibreSign application services.
Scope
Implement the minimum provider/task types needed by the currently defined LibreSign AI capability contract.
The provider should support deterministic scenarios such as:
- successful task with known output;
- malformed/invalid output;
- provider/task unavailable;
- task failure;
- cancellation where the supported contract requires it;
- delayed/asynchronous completion where relevant;
- intermediate/progress behavior only when an implemented LibreSign feature depends on it.
Do not implement fake capabilities that have no current LibreSign consumer.
Test-fixture design
Outputs must be fixture-driven and stable.
Tests should be able to request a named behavior instead of depending on prompt wording or model-like heuristics.
Examples:
- summary fixture returns a known summary payload;
- structured suggestion fixture returns a known valid payload;
- hostile fixture returns a known invalid/unsafe payload;
- failure fixture returns a controlled Task Processing failure.
Keep the test provider clearly separated from production providers and impossible to activate accidentally in a normal production installation.
Security
The deterministic provider exists to test the same trust boundaries as a real provider.
It must make it possible to verify that LibreSign:
- validates output rather than trusting it;
- does not use prompts as authorization;
- handles provider failure safely;
- rejects hostile generated markup/structured output at the correct LibreSign boundary;
- does not expose one user's task result to another actor.
CI expectations
The deterministic provider should be suitable for normal pull-request CI and focused local development.
Keep it:
- network-free;
- free of paid APIs;
- fast enough for normal CI;
- deterministic across runs;
- compatible with the supported Nextcloud test environment.
Done when
- A deterministic Task Processing provider/test double can expose the required foundation task types.
- Tests can select stable success and failure fixtures.
- It cannot be confused with or enabled as a production provider.
- It supports backend/integration and browser tests without external services.
- Security/error cases can be reproduced deterministically.
- Focused automated tests cover the provider itself.
- Lenguaje dominante
- PHP
- Estrellas
- 844
- Forks
- 176
- Merge medio
- 14 h 3 min
- PR fusionados (30 d)
- 344
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de LibreSign/libresign
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
OpenSSL engine: leaf certificates get O=Internet Widgits Pty Ltd, ST=Some-State from system openssl.cnfPosiblemente ocupada @vitormattos la tomó hace 5 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
LibreSign/libresign#9366 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 83/100
LibreSign/libresign#9007 · 2 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
LibreSign/libresign#8284 · 5 comentarios ·
Los mantenedores suelen responder en 1 día
-
frontend javascript technical debt
Dificultad 5/5 Más de una semana Aptitud para principiantes 8/100
Los mantenedores suelen responder en 1 día
Todos los issues de LibreSign/libresign
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
Automattic/blocks-engine#6318 ·
Los mantenedores suelen responder en 1 día
-
kind/enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
[remove-resource] Delete Open Course Hub, Open Multicourse Hub, and Learn2 with GitSync skeletonsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 61/100
omeka/plugin-ExhibitBuilder#160 ·