Acceptance: Allocation risk

A browser walk of the Allocation risk app on the offline local stack: GovOps advances a deal, Grove sees its own deals, and the SFF board reads without acting.

Prerequisites

  • The stack is running: npm run qa:local (or -- --fresh for untouched seed data). See offline local development.
  • Allocation risk is at http://127.0.0.1:4312. Sign in only through the direct links below.
  • A small PDF with synthetic content for the NDA upload, for example a blank page printed to PDF. Never a real NDA.

Steps

  1. GovOps sees the pipeline. Open http://127.0.0.1:4319/sign-in?seat=govops-pm&app=risk. Expected: signed in as Gil GovOps; "Grove synthetic facility B" and "Grove synthetic facility C" are listed at the NDA check. Screenshot risk-01-govops-list.png.
  2. GovOps completes the NDA check. Open "Grove synthetic facility B". Expected: current step NDA check. Tick the step-complete confirmation, attach the synthetic PDF under Signed NDAs (one or more), submit. Expected: the deal moves to Prioritization and the uploaded file is listed on the completed step. Screenshot risk-02-govops-nda.png.
  3. The upload is required. Open "Grove synthetic facility C", tick the confirmation and submit without a file. Expected: a validation message or a disabled submit; the deal stays at NDA check. Screenshot risk-03-nda-requires-file.png.
  4. Grove sees its deals. Open http://127.0.0.1:4319/sign-in?seat=prime-member&app=risk. Expected: the Grove deals, including "Grove synthetic facility A" at deal registration. Screenshot risk-04-grove-list.png.
  5. The SFF board reads only. Open http://127.0.0.1:4319/sign-in?seat=sff-board&app=risk, then "Grove synthetic facility C". Expected: the deal and its history are readable; there is no submittable form. Screenshot risk-05-sff-read-only.png.
  6. A spell-only seat has no deals. Open http://127.0.0.1:4319/sign-in?seat=spell-pm&app=risk. Expected: no deals listed, or an access message; no server error. Screenshot risk-06-no-membership.png.

Save every screenshot under .qa-local/screenshots/.

What counts as a failure

  • A sign-in link that does not land in Allocation risk signed in as the named seat.
  • A server error, a blank page after the first compile, or a failed upload of the synthetic PDF.
  • The NDA check advancing without a file, or not advancing with one.
  • sff-board or spell-pm able to submit any step, or spell-pm seeing a deal.

Known gaps

  • Step 2 changes the seed; run npm run qa:local -- --fresh before walking again.
  • Steps past the NDA check that need further uploads are not seeded; walk them by hand.