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

Version 1 Current »

  1. Development and QA Environment Transition:

    • Tests are conducted in our development environment.

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

    • 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 was promoted correctly to QA.

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

  3. Status Update in Jira:

    • If everything is satisfactory in the QA environment, we update the story or task in Jira to indicate that it is "Ready for UAT."

  4. UAT Email and Documentation:

    • Before the scheduled demo meeting, we send an email to the client with the subject "Dedicated team UAT: [Feature-name]."

    • The email includes a script document outlining test case scenarios from the demo, a list of test case scenarios performed by our team, and additional documents on Confluence.

    • The client is kindly requested to review the materials before the scheduled demo meeting.

  5. Demo Meeting:

    • The scheduled demo meeting takes place, allowing us to showcase how the feature works.

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

  6. 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.

  7. 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 "Complete" status, marking the demand as "closed."

  • No labels