Add a deterministic Task Processing test provider for LibreSign AI flows
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- PHP
- Stars
- 844
- Forks
- 176
- Avg merge
- 14h 3m
- Merged PRs (30d)
- 344
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from LibreSign/libresign
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
OpenSSL engine: leaf certificates get O=Internet Widgits Pty Ltd, ST=Some-State from system openssl.cnfPossibly taken @vitormattos claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LibreSign/libresign#9366 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
LibreSign/libresign#9007 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LibreSign/libresign#8284 · 5 comments ·
Maintainers usually reply within 1 day
-
frontend javascript technical debt
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
All issues in LibreSign/libresign
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Automattic/blocks-engine#6318 ·
Maintainers usually reply within 1 day
-
[remove-resource] Delete Open Course Hub, Open Multicourse Hub, and Learn2 with GitSync skeletonsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
35-feedback
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day