Testing process for tickets (tasks)

Tickets, which are ready for testing, are located in the Quality Assurance group.

If a tester takes a task, they need to assign themselves as the Assignee.

This way, other testers will see that the task is already in test and can pick other tasks in the Quality Assurance group.

Priority should be given to tasks that need testing on production, then on stage, and then on the development environment.

Before testing, it is necessary to analyze the task. If there are any questions regarding the requirements, they can be asked to the ticket author or the Project Manager.

If changes are not displayed on the test environment, it's essential to ensure that the problem is not related to old cache or cookies (clearing them and trying in incognito mode may help).

After testing, a comment should be added to the ticket, specifying:

• ·       Test environment (e.g., Tested on Dev/Stage/Live);
• ·       Overall test result (Test Passed/Test Failed);
• ·       Brief description of tested changes and checks;
• ·       Attach screenshots/videos or other relevant files if applicable.

If a bug is found during testing (on any dev, stage, or live environment) related to the task, after writing a comment, the task should be set to the "In Progress" status and assigned to the developer who worked on it (this will be displayed in the task history). If necessary, task can be assigned to the ticket author for verification (can be clarified with the Project Manager) with the "Feedback" status.

If a bug is found that is not related to the task, a separate ticket for the bug can be created.

If the task is completed on the Dev environment, and no bugs related to the task are found, after commenting about testing on the Dev environment, the task should be moved from "Test Dev" to "Move to Stage" status and assigned to the developer.

If the task is completed on the Stage environment, and no bugs related to the task are found, after commenting about testing on Stage, if necessary, it can be assigned to the ticket author for verification (can be clarified with the Project Manager) with the "Feedback" status.

If the task is ready for installation for the Live environment, the task's status should be changed to "Ready to install," and Assignee should be set to "System Administration."

For projects in Canada or Australia, before that, the task should be linked to the release ticket, and the task's description should be added to the corresponding release ticket (link to the ticket, title, and relevant screenshot if applicable). If the ticket was previously installed on production but was returned for further improvements, it should also be linked to the next release ticket where it will be installed.

If the task is completed on the Live environment, and no bugs related to the task are found, after commenting about testing on Live, if necessary, it can be assigned to the ticket author for verification (can be clarified with the Project Manager) with the "Feedback" status.

At the final stage on production, if everything is correct, and no further actions are required, the ticket is set to "Closed" status.

The Head of QA and Testing Department close the release ticket after all tasks are completed.