When I bring it up and judge it, he will talk about the demand first.
I read the test points he wrote yesterday, which mainly focused on the specific function points of each module and could not reflect the verification of the overall business logic.
There was a project before, and two children were arranged to take the exam. A few days later, I asked them how the exam went. They said they had finished the exam, and then there were no other questions except a few irrelevant questions.
Then I tried to run a complete business process on it, but it didn't work. I won't mention the details. So in the discussion about how to write test cases in the previous two days, I have always stressed that the most important thing in this initial iteration is to verify the business logic.
At the afternoon meeting, the test engineer strung the requirements according to the business scenario, and it can be seen that his understanding of business logic should be consistent with that of the requirements analyst.
In the process of his speech, the requirements analyst has an additional perspective. When thinking about requirements from a bystander's point of view, he can find out what he didn't describe clearly before, and what some testers did not notice but mentioned in the process of requirements communication.
Because there are not many function points in this iteration, the meeting time of this review is only about 20 minutes, which is a simple but effective meeting.
Try to draw lots next time to decide who will talk about demand.
Try some fresh and effective forms in the future.