[api-test] Consent + captcha e2e coverage for mock plugin #2276

Activity

1. rachik-hue

   assigned

   nandhu-kumar

   on Aug 3, 2026
2. rachik-hue

   added

   API_Automation

   on Aug 3, 2026
3. rachik-hue

   added the

   Bug

   issue type on Aug 3, 2026
4. rachik-hue

   set

   Priority

   to

   Medium

   on Aug 3, 2026
5. rachik-hue

   added this to the eSignet_v2.0.0 milestone on Aug 3, 2026
6. rachik-hue

   added a parent issue on Aug 4, 2026

   • Add plugin-based API integration test rig for esignet-service (black-box, deployable as a CronJob with HTML reporting) #2120
7. nandhu-kumar commented on Aug 12, 2026

   

   nandhu-kumar

   on Aug 12, 2026

   ContributorAuthor

   More actions

   PR #2357 (open) closes this: captcha + consent e2e scenarios landed in e2e-scenarios.json and consent-config.feature, live-validated against the mock deployment.
8. nandhu-kumar commented on Aug 24, 2026

   

   nandhu-kumar

   on Aug 24, 2026

   ContributorAuthor

   More actions

   Delivered by #2357, merged 2026-08-21 into develop-go as 8252fa0. The Closes #2276 keyword did not fire because that PR merged into develop-go rather than the default branch, so closing manually.

   data/scenarios/e2e-scenarios.json carries all seven scenarios — captcha positive/negative, and consent prompt / stored-reuse / re-prompt-on-scope-change / deny-optional / deny-essential — plus the provider-agnostic data/features/client-mgmt/consent-config.feature for the consent_expire_in_mins / purpose additionalConfig validation. All pass against the mock deployment as of the full run on 2026-08-24.

   The consent cases are order-dependent by design and share one registered client per run: the stored-consent-reuse case asserts that no prompt appears, which only holds because the identical-scope case ran immediately before it. Each other case uses a distinct scope set so its request hash differs and the server re-prompts. Reordering them, or narrowing a run with e2e.include so the approve-all case is skipped, will make the reuse case fail. This is documented in the spec _comment and in docs/e2e-scenarios.md.
9. nandhu-kumar

   closed this as completedon Aug 24, 2026