Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Characterize signer removal consistency across envelope documents

Aperta
  • Qualcosa non va?
#9,085 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
78/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
php
Ambito
backend, testing

Direzione di ricerca

Start with tests/integration/features/sign/cancel.feature, then read the envelope fixtures and validation steps in file/envelope.feature and file/validate.feature. Add Behat coverage for removing one of two pending signers and for removing the only pending signer from a two-document envelope, checking participant identity and resulting child states. Done means both cases verify consistent envelope and child associations with no orphaned signing requests.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

backend php

Goal

Verify that removing a pending signer from an envelope consistently updates the envelope and all associated child documents.

Test approach

Extend tests/integration/features/sign/cancel.feature, reusing the envelope fixtures and validation steps already available in file/envelope.feature and file/validate.feature.

Multiple participants
  1. Create an envelope with two PDF documents and pending signers A and B.
  2. Retrieve the envelope and verify the participants associated with each child.
  3. Remove A using the authorized management operation.
  4. Reload the envelope and its children.
  5. Verify A is absent everywhere and B remains associated with both documents.

Assert participant identity instead of relying solely on array positions.

Last pending participant
  1. Create another two-document envelope with only signer A.
  2. Remove A.
  3. Reload the envelope and both children.
  4. Verify that no orphaned signing requests remain and that their resulting states are consistent with the existing workflow rules.

Boundaries

  • Prefer Behat exclusively.
  • Use only two documents.
  • Do not add benchmarks, stress tests or new reusable test frameworks.
  • Do not introduce transaction or cache refactors without a demonstrated failure.
  • Do not expand this issue into partially signed envelope scenarios requiring artificial failures.

Result and handoff

If the tests pass, submit regression coverage for normal review.

If they reveal inconsistent or orphaned associations, preserve the failing test commit, capture the before-and-after state and request maintainer review.

Do not merge failing tests. A product correction is a subsequent decision, and the reproduced test must be incorporated into the eventual fix.

Lingua principale
PHP
Stelle
830
Fork
161
Merge medio
7h 3m
PR unite (30g)
494

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di LibreSign/libresign

Tutte le issue di LibreSign/libresign

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.