Is it necessary to do code review to test the code that students participated in the development of?

Questions

Nowadays, many large factories will require testers to participate in code review of the code developed during the iterative process, and also require the ability to read code during the interview.Some students are very confused. It is enough for the testing position to do their own testing work. Is it necessary to participate in code review?Even if you read the code, can you really find the problem in the coding?

Discussion

In fact, from the perspective of quality assurance, walking code is helpful for testing.I think there are several benefits:

1. Familiar with back-end code logic, call link
2. Identify coding stage risks, such as some bad habits, exception capture problems
3. Analyze the underlying causes of bugs
4. Familiar with common pits will help to quickly identify high-risk modules that are prone to bugs

The final product should be to help test students design test cases or test methods that are closer to the core.

Generally speaking, my team asks testers to do two types of code readings:

1. The core logic code of day reading iteration

• Understand the code link corresponding to the core main link, or understand the dependencies between applications in a microservice scenario
• Describe at least one branch logic (up to method level)
• What use cases need to be designed to cover this code branch

2. Reading code related to typical back-end bugs

• Learn why the bug occurs, because what conditions trigger the bug
• Develop methods and logic for repair
• List bugs caused by similar reasons
• What use cases need to be designed to cover this code branch

At present, most of what we do is mainly based on the back-end code of java. The front-end code has not been read. Of course, if we do, it is a similar idea.

I hope this discussion is helpful to you, you can feel free to private message me for further communication~