After the test task is identified, the test engineer communicates with the agile development team members to determine their respective test tasks.
In an agile team, there is no test supervisor or test team leader in the traditional sense. The tasks of the test engineer may be assigned by the project manager, or even by the members themselves.
[Case 3-1 ECShop test task allocation]
Test engineers Lin and Xu, according to the Sprint plan content and development engineer task assignment, negotiate how to allocate the test tasks in the current Sprint.
The list of ECShop needs to be developed is shown in Table 3-1 and Table 3-2.
Table 3- 1 ECShop platform background function requirements list
Table 3- 2 ECShop platform front-end functional requirements list
According to the overall product development plan, the first Sprint only includes back-end product management, back-end membership, front-end user registration, login, and personal center functions. Lin and Xu combined their respective experience and technical level to assign tasks, as shown in Table 3-3.
Table 3- 3 Test task allocation table
After the test task is assigned, the test engineer needs to inform all members of the agile development team of the task assignment so that the team members can understand the work content of the test engineer.
After the tasks are assigned to the test, the test engineers carry out their work according to the assignment of the test tasks. Under normal circumstances, the daily work of a test engineer is mainly: familiarization with product requirements, analysis and test requirements, test case design, test case execution, defect tracking processing, daily report filling, etc. The specific affairs need to be determined according to the actual work.
When being familiar with product requirements, test engineers should not only focus on their own test modules, but should be as familiar with all requirements as possible. In the actual test work, in order to solve the problem of mindset, test engineers can implement exchange tests.
The software testing work itself is a highly repetitive work. In the process of multiple iterations, it often results in the test engineer's mindset, unable to find the defects in the system.
At this time, test engineers communicate with each other and perform exchange test tasks. Because everyone has a different thinking mode, they can give full play to their subjective initiative and find defects that others cannot find.
Exchanging tests can play a complementary role in finding more defects, thereby improving the quality of test work. Therefore, when a test engineer is familiar with requirements, in addition to being familiar with his own business to be tested, he should also deepen his understanding of other business modules.
After being familiar with the requirements, the test engineer can work on use case design.
Many companies require employees to write daily work reports every day, and have certain templates, which can be filled in according to the actual situation in actual work.