单元测试，粗略地说，就是在与测试代码隔离的情况下测试代码。我想到的直接优势是:

测试的运行变得自动化和可重复 您可以在更细粒度的级别上进行测试，而不是通过GUI进行点击测试

请注意，如果您的测试代码写入文件、打开数据库连接或在网络上执行某些操作，则更适合将其归类为集成测试。集成测试是一件好事，但不应将其与单元测试混淆。单元测试代码应该简短、简单且易于执行。

另一种看待单元测试的方法是先编写测试。这被称为测试驱动开发(简称TDD)。TDD带来了额外的优势:

您不需要编写推测性的“我将来可能需要这个”代码——只要能够通过测试即可 您编写的代码总是会被测试覆盖 通过先编写测试，您不得不考虑如何调用代码，从长远来看，这通常会改善代码的设计。

如果你现在还没有做单元测试，我建议你现在就开始做。找一本好书，实际上任何xUnit-book都可以，因为它们之间的概念可以很好地转换。

有时编写单元测试会很痛苦。当出现这种情况时，试着找个人来帮助你，并抵制住“只写该死的代码”的诱惑。单元测试很像洗碗。这并不总是令人愉快的，但它让你的比喻厨房保持干净，而你真的希望它干净。：）

编辑:我想到了一个误解，虽然我不确定它是否普遍。我曾听一个项目经理说过，单元测试让团队把所有的代码都写了两次。如果它看起来和感觉是那样的，那么，你做错了。编写测试通常不仅可以加快开发速度，而且还为您提供了一个方便的“现在我完成了”指示器，否则您就不会有这个指示器。

这回答了为什么您应该进行单元测试。

下面的三个视频涵盖了javascript中的单元测试，但一般原则适用于大多数语言。

单元测试:现在的几分钟将节省几小时后- Eric Mann - https://www.youtube.com/watch?v=_UmmaPe8Bzc

JS单元测试(非常好)- https://www.youtube.com/watch?v=-IYqgx8JxlU

编写可测试的JavaScript - https://www.youtube.com/watch?v=OzjogCFO4Zo

Now I'm just learning about the subject so I may not be 100% correct and there's more to it than what I'm describing here but my basic understanding of unit testing is that you write some test code (which is kept separate from your main code) that calls a function in your main code with input (arguments) that the function requires and the code then checks if it gets back a valid return value. If it does get back a valid value the unit testing framework that you're using to run the tests shows a green light (all good) if the value is invalid you get a red light and you then can fix the problem straight away before you release the new code to production, without testing you may actually not have caught the error.

So you write tests for you current code and create the code so that it passes the test. Months later you or someone else need to modify the function in your main code, because earlier you had already written test code for that function you now run again and the test may fail because the coder introduced a logic error in the function or return something completely different than what that function is supposed to return. Again without the test in place that error might be hard to track down as it can possibly affect other code as well and will go unnoticed.

Also the fact that you have a computer program that runs through your code and tests it instead of you manually doing it in the browser page by page saves time (unit testing for javascript). Let's say that you modify a function that is used by some script on a web page and it works all well and good for its new intended purpose. But, let's also say for arguments sake that there is another function you have somewhere else in your code that depends on that newly modified function for it to operate properly. This dependent function may now stop working because of the changes that you've made to the first function, however without tests in place that are run automatically by your computer you will not notice that there's a problem with that function until it is actually executed and you'll have to manually navigate to a web page that includes the script which executes the dependent function, only then you notice that there's a bug because of the change that you made to the first function.

重申一下，在开发应用程序时运行测试将在编写代码时发现这类问题。如果没有适当的测试，你必须手动检查整个应用程序，即使这样也很难发现错误，你天真地将其发送到生产环境中，一段时间后，好心的用户会给你发送错误报告(这不会像你在测试框架中的错误消息那样好)。

It's quite confusing when you first hear of the subject and you think to yourself, am I not already testing my code? And the code that you've written is working like it is supposed to already, "why do I need another framework?"... Yes you are already testing your code but a computer is better at doing it. You just have to write good enough tests for a function/unit of code once and the rest is taken care of for you by the mighty cpu instead of you having to manually check that all of your code is still working when you make a change to your code.

此外，如果你不想进行单元测试，你也不必进行单元测试，但随着你的项目/代码库开始变得越来越大，引入错误的可能性也在增加，这是值得的。

单元测试是关于编写测试应用程序代码的代码。

名称的Unit部分是关于一次测试小单元代码(例如一个方法)的意图。

xUnit是用来帮助测试的——它们是帮助测试的框架。其中一部分是自动测试运行器，它会告诉您哪些测试失败，哪些测试通过。

它们还可以在每个测试之前设置您需要的公共代码，并在所有测试完成后将其删除。

您可以使用一个测试来检查是否抛出了预期的异常，而不必自己编写整个try catch块。

我在大学里从未学过单元测试，我花了一段时间才“学会”它。我读到它，心想“啊，对，自动化测试，我想那应该很酷”，然后我就忘记了。

It took quite a bit longer before I really figured out the point: Let's say you're working on a large system and you write a small module. It compiles, you put it through its paces, it works great, you move on to the next task. Nine months down the line and two versions later someone else makes a change to some seemingly unrelated part of the program, and it breaks the module. Worse, they test their changes, and their code works, but they don't test your module; hell, they may not even know your module exists.

现在你有了一个问题:坏代码在主干中，甚至没有人知道。最好的情况是内部测试人员在您发布之前就发现了它，但是在游戏后期修复代码的成本很高。如果没有内部测试人员发现它……嗯，这确实会非常昂贵。

The solution is unit tests. They'll catch problems when you write code - which is fine - but you could have done that by hand. The real payoff is that they'll catch problems nine months down the line when you're now working on a completely different project, but a summer intern thinks it'll look tidier if those parameters were in alphabetical order - and then the unit test you wrote way back fails, and someone throws things at the intern until he changes the parameter order back. That's the "why" of unit tests. :-)

我想推荐Gerard Meszaros的《xUnit测试模式》一书。它很大，但在单元测试方面是一个很好的资源。这里有一个链接到他的网站，在那里他讨论了单元测试的基础知识。http://xunitpatterns.com/XUnitBasics.html

单元测试是在不需要该代码单元所依赖的基础设施的情况下对代码单元(例如单个函数)进行测试。即在隔离环境中进行测试。

例如，如果您正在测试的函数连接到数据库并执行更新，那么在单元测试中您可能不想执行该更新。如果这是一个积分测试，你会这样做，但在这个例子中，它不是。

因此，单元测试将测试您正在测试的“函数”中所包含的功能，而不会产生数据库更新的副作用。

假设函数从数据库中检索了一些数字，然后执行标准偏差计算。你想测试什么?标准偏差计算正确，还是数据从数据库返回?

在单元测试中，您只想测试标准偏差的计算是否正确。在集成测试中，您希望测试标准偏差计算和数据库检索。