Test execution ACC environment - NextensArelB/SwaggerGenerationTool GitHub Wiki

Objective To validate whether the upcoming release is working in production like environment and if there is no negative impact on existing functionality (=regression test)

Who QA of release and QA of impacted teams

What Execution of a smoketest for the release and the impacted assets of other teams (manual and/or automated)

When When the testing on DLV is complete and the release is ready to go live, a final production like test will be performed on ACC environment, here a subset (=smoketest) of selected tests are performed, preferably as much as possible automated, however some manual, visual tests are performed.

How

• Inform teams on the upcoming release, the planning, the changes and impact:
  • When there is a small impact, it can be sufficient to share this in the teams channel and tag the impacted teams
  • When there is a huge impact, schedule a meeting with the QA's of impacted teams and inform them on the changes and impact and align on planning
• When functionality is merged to ACC:
  • Prepare test data (if applicable)
  • Perform smoketest of the US (manual and/or automated)
  • Ask impacted teams to perform their smoketests (manual and/or automated)
• In case of deviations, determine if it is a bug (described in US) or a change (not described in US)
  • Create bug or task on the board
  • Discuss or inform DEV on bug/taks found
• When testing on ACC is complete, inform DM and rest of the team of the result

Tools

• Management Portal
• DevOps tasks or test cases
• DevOps bugs