Testing notes (QA Tester)
Shall start testing by the end of each sprint upon deployment to testing environment to verify the correctness of agreed deliverables periodically using the frontend channels UI (WEB | MOBILE) as a final end user.
Upon detecting a malfunction upon testing from the UI (WEB | MOBILE) the finished tickets at the end of each sprint, the ticket shall reopened and assigned back to the UI (WEB | MOBILE) development team.
Ticket assignee transition AKA escalation to another team in our case the backend development team:
The UI (WEB | MOBILE) development team shall reassign the ticket to the backend development team during the daily standup upon notifying the Scrum Master (Team Lead) about this transition and adding a useful comment on the ticket to start investigating from the backend development team end effectively.
If a malfunction found via any reopened ticket, then upon resolving the issue the branch name should be like feature-branch_ticket-number_fix_[N] where N is defined as a resolving issue number and it starts count from 1 till N.
Note that you shall be given a real data to simulate actual scenarios on a system under-construction.