单元测试是否必要？

最新推荐文章于 2024-05-03 04:04:10 发布

原创最新推荐文章于 2024-05-03 04:04:10 发布 · 3.3k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#单元测试 #testing #go #up

程序设计同时被 3 个专栏收录

72 篇文章

订阅专栏

项目管理

22 篇文章

订阅专栏

测试

10 篇文章

订阅专栏

本文探讨了单元测试的价值，将其比作健身过程。初期可能会感到困惑和疲惫，但随着时间推移，会认识到其对代码质量提升的重要性。文章指出，对于处理 spaghetti 代码基础的公司，单元测试可能需要大量努力；而对于试图引入单元测试到工作流程中的人来说，如果遇到与预期不同的挑战，可能需要寻找新的工作环境来更好地实现单元测试。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Is Unit Testing worth the effort?

Unit testing is a lot like going to the gym. You know it is good for you, all the arguments make sense, so you start working out. There's an initial rush, which is great, but after a few days you start to wonder if it is worth the trouble. You're taking an hour out of your day to change your clothes and run on a hamster wheel and you're not sure you're really gaining anything other than sore legs and arms.

Then, after maybe one or two weeks, just as the soreness is going away, a Big Deadline begins approaching. You need to spend every waking hour trying to get "useful" work done, so you cut out extraneous stuff, like going to the gym. You fall out of the habit, and by the time Big Deadline is over, you're back to square one. If you manage to make it back to the gym at all, you feel just as sore as you were the first time you went.

You do some reading, to see if you're doing something wrong. You begin feel a little bit of irrational spite toward all the fit, happy people extolling the virtues of exercise. You realize that you don't have a lot in common. They don't have to drive 15 minutes out of the way to go to the gym; there is one in their building. They don't have to argue with anybody about the benefits of exercise; it is just something everybody does and accepts as important. When a Big Deadline approaches, they aren't told that exercise is unnecessary any more than your boss would ask you to stop eating.

So, to answer this question, Unit Testing is usually worth the effort, but the amount of effort required isn't going to be the same for everybody. Unit Testing may require an enormous amount of effort if you are dealing with spaghetti code base in a company that doesn't actually value code quality. (A lot of managers will sing Unit Testing's praises, but that doesn't mean they will stick up for it when it matters.)

If you are trying to introduce Unit Testing into your work and are not seeing all the sunshine and rainbows that you have been led to expect, don't blame yourself. You might need to find a new job to really make Unit Testing work for you.