Unit testing is to write test code, and it should accurately and quickly ensure the correctness of the basic module of the program. The standard for good unit testing, JUnit is the Java unit testing framework, which is installed by default in Eclipse.
Unit test benefitsMany developers have a habit and are often reluctant to write a simple unit test program to validate their code. I have been very confident in my own program, or there is a chance to throw it into the test group and test it directly after each run. However, each time the test group's BUG is submitted, it will find that there are still many vulnerabilities in the program. But after every revision of the BUG, ​​I still have the luck and think that there will be no bugs this time.
Then I submitted it confidently again and the result was defeated. Because this is repeated several times. Developers are spending more time looking for bugs and fixing bugs than they have spent developing this module. Although the project manager has reserved time to modify the bug and unit tests. But developers are habitually thinking that the task is complete after writing the code. Then when the problem came out, the bug changed a lot of times or it couldn't be fixed, and then the project manager said, "I have an unexpected problem, I may postpone the release of my code." If this project cannot be postponed, painful overtime can't be avoided.
Why are there so many BUG developers who haven't found out? In fact, developers are people and not machines. People can not escape from doing wrong. BUG is inevitable, but every time before fixing a bug, it is basically impossible to know which piece of code the bug is causing. Each time you locate a bug, it can take you an hour or a day, depending on your level. But if your core program has unit test code.
You won't need to rely on your experience to judge or guess which program the bug is caused by. Just run your unit test method. BUG can be easily located by simply judging the results of the test method. So on the surface, writing test code for each unit program seems to increase the workload, but in fact, these codes not only woven a protection net for you, but also help you quickly locate errors so that you greatly reduce Fix the time of the bug. And this is also good for your health, you will not be painful because you can't find a BUG, ​​and you will not have to work overtime without sleep. And the progress of the project will be under control.
In fact, unit testing not only ensures project progress but also optimizes your design. Some developers will say that writing unit test code is too laborious and more troublesome than writing business code. However, if you force the developer to write unit test code. Developers who are smart and want to 'lazy' can write test code more easily in the future. The only way is to optimize the design and design the business code as much easier as possible. Slowly developers will find out. The degree of program coupling designed by myself is also getting lower and lower. The input and output, business content and exceptions of each unit program are as simple as possible. Finally, I found that my programming habits and design skills are getting more and more sophisticated.
In fact, the code that is easy to test can basically be equated with the well-designed code. Because a unit test case is actually the earliest user of a unit. Easy to use obviously means good design.
Well-designed projects have always focused on code reuse. The benefits of code reuse are not mentioned here. But to do code reuse, first of all, to ensure that the reused unit program must be a very good program, in addition to good design, there must be detailed documentation. The most important thing is actually the unit test code.
I don't know if you have such an experience? When you don't know how to use an API function to find help with a document, you will often skip the large paragraph of the English description and go directly to the sample program provided in the document, and then call this in your own program. function. So, do you realize that the code being reused has unit test code. Your test code can be the best API for this function.
Unit test code can also be used to test real-world data in a production environment with a simple transaction rollback function without worrying about generating unnecessary data. With such test code we can check if the previous release was successful after the program was released. In the past, we often encountered a rather embarrassing situation. When we released the program to the formal environment, we all still had a little worries. Because we can't run our program on a formal environment, we can only passively wait for the client to operate before we know if the released program is normal.
This situation makes us very passive. If we are lucky, there may be no problem, but once the customer finds a system error or error data in the formal environment, the consequences are very serious, which will affect The reputation of the product is obviously so boring. If we run the unit test code, we can proactively discover and modify it and re-release it if there is a problem. Sometimes, even if there is a problem, it may be a relatively low-level error, or it may be caused by a release problem. It will basically be solved soon! So we don't have peace of mind!
Many studies have shown that the later the bug is discovered, the higher the cost of modifying it, so from a cost perspective, the bug should be looked up and modified as early as possible. Maybe someone will have an objection? The programmer found out all the bugs. What about the test group? In fact, the test group is doing integration testing, such a test can not fully consider the various input parameters used when each unit is called. Just like a car, testing every part is a must. Testing an assembled car is not a substitute for individual testing of each part. Perhaps testing an assembled car can reveal problems with certain components. But when you find the problem at this time, you need to remove the car and replace it. The cost is imaginable.
After paying attention to unit testing, you will find that the benefits of unit testing are much more than that. At present, when the team development under java adopts the mode of cvs (version control) + ant (project management) + junit (integration test), the test automation can be very simple by configuring ant. Among all agile software development methods, XP (Extreme Programming Extreme Programming, a lightweight, savvy software development method) is currently the most widely used one. The implementation of Test First Design, which is highly respected in XP, already has The off-the-shelf development means: "Write the test code with JUnit, write the implementation code, run the test, test the failure, modify the implementation code, and then run the test until the test is successful. After the code modification and optimization, the test is successful, the modification is successful. "When developers are used to such development tools, bringing them to developers will be a pleasure!"
Ic Data Acquisition,Data Acquisition Analog Front End,Data Acquisition Analog To Digital Converters,Data Acquisition Digital To Analog
Shenzhen Kaixuanye Technology Co., Ltd. , https://www.iconline-kxy.com