Skip to content

Testing and QA workflow

Jump to bottom
Simona Domnisoru edited this page May 19, 2022 · 12 revisions

As part of the capture-app continuous deploy and release process, we need to ensure that all PRs are tested by QA before we merge them. Some exceptions to the default process are Dependabot PRs, Transfix PRs, and PR which made no changes to the logic of the app.

The workflow after the PR review is complete

Successful testing

  1. Dev adds “preview” label to the PRs (including backports) and advances the JIRA-ticket to “testing”. When advancing the JIRA-ticket to “testing” we should assign it to someone. Most of the time this someone is Geetha. One exception is when Gintare made the ticket, then it makes sense to assign it to her.

  2. QA will do their testing. If successful, they will assign the ticket back to the dev and add a comment (about the successful testing)

  3. Dev will merge the PRs (including backports) and finally set the JIRA-ticket to “Done”.

Needs update

If QA finds that a PR needs an update in step 2, they will set the JIRA-ticket to “Needs update” and assign the ticket to the dev. Dev will do her/his magic. After completing the magic (PR ready for re-testing), the dev should:

  1. Remove and then re-add the “preview” label (to redeploy the app to Netlify)

  2. Once again advance the JIRA-ticket to “re-testing”.

Clone this wiki locally