UAT Flow

Owned by Hellen Rodrigues Magalhaes
Last updated: Nov 27, 2023

 

  1. Development and QA Environment Transition:

    • Tests are conducted in our development environment

    • Weekly (very often on Tuesdays), the demand that we have merged on master is moved to the QA environment, regardless of its readiness for UAT. If the demand is not done, it means we are still addressing issues or bugs.

    • However, the demand is protected by a feature toggle, requiring the client to activate it to experience the new feature.

  2. Smoking Test in QA:

    • Once deployed in the QA environment, our development team performs a smoke test to ensure the feature is promoted correctly to QA.

    • Smoke testing is only performed when the demand is complete and has been promoted to the QA environment.

    • If everything is satisfactory in the QA environment, we update the story or task in Jira to "QA Ready” status, which means Ready for UAT.

  3. Demo Meeting:

    • We have pre-scheduled demo meetings every 15 days, however, it is necessary to re-send the invite with the subject and add stakeholders.

    • For most demands, a demo meeting is conducted to showcase how the feature works.

    • Quick feedback is gathered during the meeting, and any necessary adjustments are discussed and aligned.

  4. Documentation and Feedback Request:

    • A script document outlining test case scenarios from the demo, a comprehensive list of test case scenarios performed by our team, and additional documents on Confluence are shared via email. The subject of the email must be "[RBI Dedicated team] UAT <Feature-name>."

    • The demo meeting recording must be shared too.

    • In this email, the client is kindly requested to provide feedback on the presented features.

  5. Production Environment Transition:

    • Similar to the QA environment, the demand is also deployed to the Production environment automatically.

    • However, the feature is only active in the production environment when the client explicitly requests us to turn it on.

  6. Client Activation and Closure:

    • The client's activation request is made by responding to the UAT email, ensuring organized communication.

    • Upon receiving the client's request to turn on the feature, the story or task in Jira is moved to the “UAT Complete” > "Complete" status, marking the demand as "closed."