Skip to end of banner
Go to start of banner

Vega UAT Readiness Guide [DRAFT]

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

This page is to highlight key tasks and team roles and responsibilities when preparing for and during a UAT.

Vega UAT environment: https://folio-perf-vega-2nd-consortium.ci.folio.org/ Login credentials available upon request.

UAT Documents: User Acceptance Testing

Task

Team role

Notes

Develop UAT concept, document steps to test key functionality, create Microsoft Forms survey

PO

 

Review UAT document and ensure development work is complete in order to successfully run UAT

BE, FE, Manual QA

Team member to alert PO with any concerns.

Create test Users with correct permissions

Manual QA

PO will provide count of Users needed

Create necessary data in environment (e.g., Requests, Users)

BE and / or FE; PO; Manual QA; SM guidance

PO to provide data requirements; SM to confirm with Team who will complete this step for each UAT

Test work after creating Users with correct permissions

Manual QA (first); PO

 Manual QA to alert PO when ready to go

Daily manual launch of UAT environment

FE; BE

Environment to function between 3 AM and 5 PM EST (M-F)

Daily check to ensure UAT environment is generally functioning

PO

Notes:

  • Team will alert SM of any issues with development or environment that can impact the start or progress of the UAT, and he will alert others, including POs.

  • No labels