How We Manage Testing Process in Trendyol International Team?

Hello everyone :)

In this post, I will provide information about how we manage the Testing Processes in the International Team where I work in the Software Developer in Test (SDET) role.

• Our QA Team consists of 4 Software Developers in Test (SDET).
• -Each SDET executes both Automation and Manual Testing process.

I will explain our Testing Process in two steps;
1.Job Tracking and Test Steps
2.Weekly Meetings

1.Job Tracking and Test Steps

There are two Job Tracking Boards for which the QA Team is responsible.

Development Board
It is the board used jointly with the development team (Developer, Product Managers).
Two fields are used to assign tasks on this board.
Assignee: The Software Developer info who will work on the task.
Test Assignee: The Software Developer in Test info who will work on the task.

QA Board:
It is the board where the testing processes related to the tasks are followed.
After the QA Grooming Meeting, each SDET opens the task it will test on the Development Board to the QA board .
In this board, the Assignee field is used for SDETs.

The design and used columns for the QA Board are as follows;

TO DO: Tasks that are ready for the testing process are in this column. Each SDET can see the tasks it is responsible for in this column.

HANDSHAKE: After the QA Grooming meeting, each SDET makes a short review with each task’s developer for the tasks it is responsible for and checks whether there is a missing point (Design, Test data, Related contact info etc.) about the task. If there is any missing point, the Product Manager or technical Lead is contacted.

TEST CASE: At this stage, manual test cases are written for the tasks.

EXECUTION: At this stage, manual tests are run for the tasks that are ready for testing.

AUTOMATION: At this stage, automation tests are written after manual tests have been completed.

REVIEW: At this stage, after the automation tests are written, they wait for review to merge into master.

2.Weekly Meetings

Weekly internal meetings of the QA Team in a Sprint;

QA Grooming Meeting

• It happens after the Grooming meeting with the Development team.
• For the testing process of the tasks included in the next Sprint, a Test Assignment process is performed between SDETs.
• At this meeting, test efforts are determined for the task.
• The duration of this meeting is 30 minutes.
• Apart from SDETs, Tech Lead also can attend this meeting if he/she wishes.

QA Planning Meeting

• It happens after the Sprint Planning meeting with the Development Team.
• Before the sprint starts final checks are made for the tasks and it is checked if there is anything missing.
• A new Sprint is started on the QA Board.
• In this meeting, “For which tasks should automation be written?” the question is answered.
• The duration of this meeting is 30 minutes.
• Apart from SDETs, Tech Lead also can attend this meeting if he/she wishes.

QA Daily Meeting

• At this meeting, each SDET answers the following 3 questions,

-What did I do yesterday?

-What will I do today?

-Is there any trouble during the testing process?

• The duration of this meeting is 15 minutes.
• Apart from SDETs, Tech Lead also can attend this meeting if he/she wishes.

We can summarize our testing process and meetings as follows

Thank you for reading, see you in the next post :)