After the completion of the project (there are more function points), is it not suitable for unit testing?

doesn"t fit?
what are we going to do?
it doesn"t seem to work without testing

Jul.01,2022

Project has been finished, you also test a hammer ah? The so-called unit test itself is an indispensable part of TDD, which refers to a process in which the test cases are first written according to the requirements and prototypes, and then the project code is gradually completed according to the test cases when the project has not yet started. When the project is completed, it goes directly to the system test, and what unit test should be done at this time?


Unit test is one of the means of testing. You can also click with the mouse to test
writing a single test breakfast is more valuable, because the problem has been found earlier.
there are many excuses for not writing a single test. The common problem is cost (labor cost and time cost)
if your project has been manually tested by qa, the value of make-up single test is indeed lower
if you pursue quality. But time is limited, you can pick the code to test
priority testing tool code, the code that is used in many places, the ugly and complex code that may have problems, and the code with high business value


the ut of the front-end project is not necessarily executed before the project starts, right? Such as the ut of some react components or the ut of the util method.


Unit testing is mainly used in some open source projects. General requirements for the project, use, may write use cases for the workload is greater than your development workload.


No, unit tests can be carried out for a single function point, and hidden bug can be detected, especially whether many boundary conditions are missing


.

after the project is finished, it also depends on the maintenance value of your project. If your project is of great maintenance value in the future (for example, it will take a long time and is likely to add modification features),
I think it is necessary to add test cases.

the most important purpose of writing unit tests is to "give yourself confidence" and give you the confidence to modify the code.
of course low coverage or poorly written unit tests will give you the illusion of "everything goes fine".

Menu