PR Review and Testing Process

Step 1. Developer Actions

• Complete fixes and create a Pull Request (PR)
• Send Vedika:
  • URL to the PR
  • URL to the staging site (found in the PR page)

Step 2. QA (Vedika’s) Actions

• Test the site on the staging environment
• Record results in the PR comment system
• If issues found → notify developer (and comment on PR)
• If no issues → inform developer so they can merge the PR

Step 3. Post-Merge Testing

• Once the PR is merged and deployed (5–7 mins automated)
• Test all production sites
• For example, in DWD test all 3 production sites:
  • DWD
  • DNV
  • IITD
• Notify the developer whether issues were found or not