RM3141-01-02 CM3141-01-02 Unit module SAT

CM3142-01-03 CX3147-04

Who will do the unit testing?
Think about it: as we explained earlier, unit testing is simply the testing of code written by developers. Since it is related to code, our first feeling is that it should be done by developers. Given that unit tests contain the word “test,” “testers do it” makes sense.
Unit testing is usually done by developers or testers. There is no absolute standard for who should do it. It depends on the actual situation of the company. Let’s look at the advantages and disadvantages of unit testing as a developer or tester:
Developers do unit testing:

Advantages: Developers are most familiar with the code, and developers have relatively strong programming skills, so developers writing their own unit tests is more efficient and has higher coverage
Cons: Developers spend a lot of time writing business code and sometimes don’t have time to write unit tests. Also, most developers don’t have a good idea of testing, and unit testing can be as simple as writing a use case; Write their own code to measure, often are unreliable!
Testers do unit tests:

Advantages: Testers have more systematic testing ideas, which can better ensure the coverage of use cases. In addition, by writing a single test, you can better understand the specific code structure and process, which is also very beneficial for the subsequent business testing.
Cons: The tester’s programming skills are relatively weak, and unit testing cannot be done without different programming. And testers are not familiar with the code developers, the efficiency will be relatively low.